PPRuNe Forums - View Single Post - WIZZ AIR Skiathos vid
View Single Post
Old 14th Aug 2022, 08:40
  #157 (permalink)  
172_driver
 
Join Date: Jan 2006
Location: Between a rock and a hard place
Posts: 1,267
Likes: 0
Received 0 Likes on 0 Posts
Can this sage advice be found in your OM-A? Does your training department advocate these techniques?
Not found in the OM-A. Not sure landing technique is described at all in the OM-A but in more operational documents, such as FCTM.
The training department condones free thinking and risk mitigation. When then the situation so warrants, you are not confined to a narrow tunnel of operating practices.

There may be other threads on professional pilots forums (somewhere?), trying to explain why the aiming pint for an AFM-compliant landing is independent of the PAPIs due to their varying location. Cue in the name: Approach Indicator.
What I think you're getting at is reachig AFM landing data?
Where my opinion deviates from others' opinion seems to be only one way of landing and always cross the threshold at 50 ft. It may be in part semantics, as the landing maneuver will look similar in profile view regardless where the trajectory will take you (and where the RA starts to shout). The amining point markers at Skiathos is about 150 m from the threshold. Runways with a length above 2400 m (is it?) has the aiming point markers at 450 m past the threshold. The threshold crossing heights can't be the same, if your objective is to land at the aiming point. The performance in-flight calculations for Actual Landing Distance from 50 ft doesn't care about the runway length. By going for the makers at Skiathos, you've earned yourself a couple of hundred meters compared to the performance figures, but you haven't crossed the threshold at 50 ft.

The video above shows many good (and similar looking) landings at Skiathos with touch downs at or near the aiming point markers. What they all have in common is the threshold crossing is a lot lower than landings at longer (and maybe wider) runways.
172_driver is offline