PPRuNe Forums - View Single Post - Stabilized App.
Thread: Stabilized App.
View Single Post
Old 6th January 2007 | 16:33
  #8 (permalink)  
Intruder
25 Anniversary
Veteran: Navy
 
Joined: May 2000
Posts: 3,204
Likes: 2
From: Seattle
Background, failed a chap on a line check (I was being observed by FAA) due to landing unspooled. He had been high on the profile the entire approach and chose to correct his position close to the airport, flare and touchdown good.
I don't quite follow this one...

How high was he? What was his descent rate? At what altitude did he retard the throttles to idle? At what altitude does your SOP require the stabilized approach to be established? Was he outside the parameters at that altitude? Were you PNF or in the Observer seat? Did you (or the PNF) make the required advisory calls (descent rate, glideslope, go around, as appropriate)?

I can see a situation where he could have been just less than 1 dot high at 1,000' AGL, with the engines somewhere above idle, kept the descent rate at 1,000 FPM, and retarded the throttles to idle somewhat earlier than normal to make that "good" flare and touchdown. If that is the case, it may have been a "bad bust."

I can also see a situation where the airplane was NOT within the allowable parameters, and the PNF did NOT make the required advisory calls. In that case, both the PF AND the PNF should have been "busted"!

So, what was "the rest of the story"?
Intruder is offline  
Reply