Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
MY FS FLIGHTS
Flight Score
Work on the flare
Arrive slow and the sink rate at the threshold is already above schedule, the flare is short because there is no energy to extend it, and the touchdown is hard in a way that feels exactly like a late flare. Diagnosing a slow arrival as a late flare is the catastrophic misread: you respond by flaring earlier, which bleeds more speed, which makes the next one worse. The tiebreaker is threshold speed against VRef, not feel. Never diagnose a flare without it.
Read more in Flare TimingStart to finish · 17 stages, 15 scored
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
The threshold, the flare and the hold-off. The approach that led to it is the stabilisation gates below.
One stabilised approach gate: five checks where the approach path is 500 ft above the runway. The 1,000 ft gate was not assessed, because the approach did not join final that far out.
Side view — the last 1,524 m of the approach.
Plan view — the first 1,524 m of the 3,837 m runway, to the same scale as the side view.
Touched down 1,073 m past the threshold — beyond the full-score zone. The arrival was smooth.
The rest of the report
The flight began with taxiing from the parking to the runway at Strasbourg Airport, LFST, which took 8 minutes and covered 4 nautical miles. Once cleared for departure, the aircraft began its takeoff roll from runway 05, eventually lifting off the ground at a speed of 98 knots. The takeoff distance covered 24% of the available runway length.
As the aircraft cleared the takeoff zone, it reached an enroute climb phase, starting from an altitude of 1,550 feet above sea level. Over the city of Holtzheim in Grand Est, France, the plane commenced its rapid ascent to 11,984 feet, increasing its altitude by 10,435 feet in a mere 4 minutes while traversing 2 nautical miles.
Following this climb, the aircraft engaged in an enroute level cruise phase, initially starting over Geispolsheim and lasting for 16 minutes. During this period, it covered a distance of 53 nautical miles. The plane then began its descent from a height of 12,825 feet to 1,956 feet at Bernwiller, a decrease of 10,869 feet in 6 minutes, covering 4 nautical miles.
After this descent, the aircraft entered a brief enroute level cruise phase over Hochstatt, which lasted for 3 minutes and covered 5 nautical miles. As the flight progressed, the plane encountered another climb phase, this time commencing 1 mile east of Wittelsheim. From an initial height of 2,222 feet, the aircraft ascended to 10,195 feet, increasing its altitude by 7,973 feet in a mere 3 minutes, covering a distance of 2 nautical miles.
The final descent phase of the flight took place over Kingersheim. The aircraft descended from 10,227 feet to 1,048 feet, a reduction of 9,179 feet in 7 minutes while covering 13 nautical miles. Upon completing this descent, the plane prepared for landing at LFH2 Bale Mulhouse.
Landing was executed on runway 15, which was 3,837 meters long. However, the threshold height was found to be excessively over the target, and the threshold speed was excessively high. Moreover, the touchdown point was located 793 meters beyond the touchdown zone, and the touchdown speed of 103 knots was deemed too fast, whereas the touchdown rate was well within acceptable limits at -157 feet per minute.
Notably, the aircraft's runway touchdown position was significantly misaligned with the centerline by 23.4 meters, and this misalignment persisted during the runway rollout, where it was found to be off the centerline by 25.6 meters. The aircraft was also affected by local weather conditions, including a temperature of 27 degrees Celsius and winds of 9 knots at 80 degrees.
The total landing distance covered 1,408 meters, which represented 37% of the available runway length. Upon completing the landing, the aircraft began taxiing from the runway to the parking area, a process that took 4 minutes and covered less than 1 nautical mile. Throughout the flight, the aircraft operated efficiently, consuming no fuel and covering a total distance of 86 nautical miles while airborne for 51 minutes.
The landing of the PC-12 at LFH2 Bale Mulhouse runway 15 was evaluated, yielding a score of 50.9%. This assessment indicated several points of non-compliance with optimal landing standards. One of the major concerns was the excessive threshold height of 148 ft above ground level (agl), which significantly surpassed the target height.
Upon further analysis, it was discovered that the threshold speed was also excessively high at 111 kt. Moreover, the touchdown point was 793 meters beyond the designated touchdown zone, indicating that the aircraft touched down too far down the runway. The touchdown speed of 103 kt was also deemed too fast, contributing to the overall unsatisfactory landing performance.
The evaluation further revealed that the runway touchdown position was significantly misaligned by 23.4 meters from the runway centerline. This error may have contributed to the difficulties in maintaining proper alignment during the runway rollout, which, in turn, resulted in a misalignment of 25.6 meters from the centerline.
The local weather conditions at the time of landing were characterized by a temperature of 27 °C and a wind speed of 9 kt at an 80° angle, resulting in a crosswind of 9 kt and a headwind of 2 kt. These conditions should not have a significant impact on the landing, given the aircraft's capabilities.
However, despite these factors, the pilot of the PC-12 still failed to achieve a satisfactory landing, as indicated by the low score of 50.9%. This highlights the need for thorough analysis and identification of key factors contributing to the poor landing performance before corrective actions can be implemented.
Scroll or drag the slider to zoom · double-click to reset · hover for values