Wedge313
Well-known member
I'm in the early stages of the Apollo 16 mission, running the RTCC calculations for MCC-1. Another learning opportunity presents itself.
I'm using Option #4. The initial calculation comes up with a 7 fps maneuver, but it gives me an LOI burn time of 74:56:35. The Flight Plan shows LOI at 74:28:38. If I adjust the F23 constraint times and move the LOI burn closer to the flight plan time (I ended up with 74:28:55) the required dV jumps up to 28.6 fps.
How important is it to get the LOI to agree with the flight plan at this point? I'd imagine being off by 27 minutes would have a huge effect on the resulting orbit. But will later MCC's give me more efficient opportunities? How do I set up the RTCC to look at the dV's that might be required later? Just by adjusting the TIG? Or is there a way to see all the MCC's at once to find the more optimal solutions? Thanks.
BTW I'm using NASSP v8-1833 this time. I like the new FDAI and the Checklist MFD EXEC ON/OFF feature. Constantly improving an already impressive product.
I'm using Option #4. The initial calculation comes up with a 7 fps maneuver, but it gives me an LOI burn time of 74:56:35. The Flight Plan shows LOI at 74:28:38. If I adjust the F23 constraint times and move the LOI burn closer to the flight plan time (I ended up with 74:28:55) the required dV jumps up to 28.6 fps.
How important is it to get the LOI to agree with the flight plan at this point? I'd imagine being off by 27 minutes would have a huge effect on the resulting orbit. But will later MCC's give me more efficient opportunities? How do I set up the RTCC to look at the dV's that might be required later? Just by adjusting the TIG? Or is there a way to see all the MCC's at once to find the more optimal solutions? Thanks.
BTW I'm using NASSP v8-1833 this time. I like the new FDAI and the Checklist MFD EXEC ON/OFF feature. Constantly improving an already impressive product.