Flying the F-14 yesterday while attempting to intercept the localizer (the start of the sequence was me having the nav set up in GPS) I was ordered to go around. During the turn and climb up to 5000 ASL the tomcat stalled the port wing which induced a roll to the left. First step in any stall recovery is to firewall the engine(s) which I did. overshot the altitude given and accerated to about 500kts and climbed about 3000 asl over assigned altitude. Oh well it happens. ATC approach controller didn’t like that so the controller issues a level 3 , which I can sorta understand why. I screwed up as I was bingo fuel and wasn’t able to set up the nav fully and missed the ILS intercept and was correcting the situation when ATC ordered the to around. The problem I have with this is that I got the level 3 while in the midst of a stall recovery. I guess ATC wants us to stall crash burn in. Sad part is with the tomcat in that situation the stall was induced by complying with ATC instructions. I accept the violation with the knowledge that ATC is unfamiliar with the stall characteristics of the tomcat. What I learned in this situation is to make sure the nav is setup prior to contacting ATC. The appeal person is another that needs to learn the stall characteristics and recovery. I also learned that I shouldn’t hand fly the tomcat in approach phase and to the autopilot.
To the controller @Bassman I was complying with your instructions, thank you for forcing an unnecessary stall recovery as I was correcting my error when you issued your premature to around instruction. We both made mistakes.
This post is meant to educate and to help others avoid the mistakes I made on that flight, not to criticize anyone else but myself. Yesterday wasn’t my day flying anything but the challenger 350 as that was my only successful flight.
I bet a feature like this to let ATC know there’s an emergency of some sort would’ve helped. Unfortunately, there just isn’t a clear way to let ATC know that something like this is happening to you, so they just assume you aren’t following instructions.
Yep would be nice. I admit I made a few errors not setting the nav system to have and was correcting. I follow the basic rules of aviation, Aviate, Navigate then communicate. I was attempting to maintain a stable approach and not decend to fast.
Your inability to fly the aircraft within its performance envelope and comply with basic ATC instructions is not a fault of the aircraft or the controller. You’ve repeated this little rant in various threads for several hours now. It’s time to buck up, put on your big boy pants and take ownership of the problem.
No. I read the childish drivel and repeated public harassment of the controllers. The replays have been reviewed by appeals and IFATC Leadership and it’s extremely clear where the issue lies. Please be respectful and cease calling out other members by name when creating content in the community.