I handled this flight poorly, too, as it involved one of those extremely rare occasions when I've been obligated to take a missed approach.
I fixed up a pretty good route out of San Juan, JETSS1 SLUGO ULUBA1 at FL290. The flight went very well, until it was time to land. Sint Maarten was fogged in. I took the RNAV approach to runway 10, but try as I might I could not see the runway in time, and took the missed approach. Unfortunately, the FMS seemed to have trouble with the missed approach procedure, and so did I.
I eventually got vectored out to where I could try again. On this try, I could actually see the runway, but only after I went missed again. I decided to try one more time.
On the third try, just when I was about to give up, I saw runway lights, and I was able to come in for a reasonable landing. I had enough fuel to go back to San Juan, but I really wasn't relishing the thought.
Another large jet went missed as I did, but a third simply landed visually at extremely low altitude. Either he had way different weather than what I had (certainly possible in simulation, if he doesn't have real weather set up the same way), or he was violating a stack of regulations. In fact, I'm sure he was violating regulations irrespective of the weather.
Anyway, I was displeased with the behavior of the FMS. I wish I had a complete manual for it. I flew everything after the first missed approach with the autopilot alone, and by hand.
For the return trip, things went more easily, since the weather in San Juan was good and the weather at Princess Juliana airport had cleared up. Unfortunately, I noticed that I had a student controller waiting at San Juan Approach, with the ominous warning in his comments that he would “not tolerance disobediance (sic),” so rather than be bossed around by a junior-high student, I completed the flight offline. I parked right where I had started earlier in the day.
- ▼ June (2)
- ► 2009 (169)