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 · 20 stages, 18 scored
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,648 m of the approach.
Plan view — the first 1,648 m of the 3,384 m runway, to the same scale as the side view.
Touched down 788 m past the threshold — beyond the full-score zone. The arrival was smooth.
The rest of the report
The flight on the Airbus A320 Neo started by taxiing from the parking area to the runway at OMRK Ras Al Khaimah Intl. The taxiing process took 3 minutes and covered less than 1 nm. The departure roll was from runway 16, with a takeoff distance of 937 m, which was 25% of the runway length. The liftoff speed was 145 kn. The local weather at the time of departure was 38 °C with a wind speed of 16 kn at 130°, leading to a crosswind of 9 kn and a headwind of 13 kn.
The enroute climb commenced over OMRK Ras Al Khaimah Intl, ascending from 1,103 ft asl to 6,240 ft asl. This climb covered 9 nm and lasted for 3 minutes. Following this, the level cruise phase began 9 miles southeast of OMRK Ras Al Khaimah Intl, lasting for 6 minutes and covering 28 nm. Another climb phase started 9 miles northwest of Ras Al Khaimah City, climbing from 6,229 ft asl to 36,195 ft asl over 18 minutes, covering 126 nm.
The subsequent enroute descent began 19 miles north of OIRU Rudan Airport Rudan, descending from 36,194 ft asl to 4,551 ft asl over 24 minutes, covering 104 nm. The landing took place on runway 30 at OIKM Bam, with a runway length of 3,384 m. The height at the threshold was 80 ft agl, with a speed of 134 kn. The touchdown occurred 742 m from the threshold, at a speed of 131 kn, with a VSI of -380 ft/m. The local weather at the time of landing was 37 °C with a wind speed of 14 kn at 99°, resulting in a crosswind of 5 kn and a tailwind of 13 kn. The total landing distance was 1,532 m, which was 45% of the runway length.
Taxiing back to the parking area from the runway took 1 minute and covered less than 1 nm. The entire flight covered a distance of 279 nm, lasting 71 minutes and using 2,191 kg of fuel.
Firstly, let's address the Approach Phase. The poor descent path above the glideslope limit suggests that adjustments need to be made to ensure a smoother descent towards the runway. This could be due to factors such as incorrect speed or altitude control. It is crucial to maintain the correct descent path to ensure a safe and efficient landing.
Moving on to the Landing Phase, the significantly high threshold height is a concern as it indicates that the aircraft was not in the optimal position for landing. Additionally, the very poor landing flare suggests that there was a lack of proper technique during the final moments before touchdown. Proper flare technique is essential for a smooth and controlled landing.
Next, in the Touchdown Phase, the hard touchdown rate raises red flags about the potential for damage to the aircraft and discomfort for passengers. Additionally, the touchdown point being 336 meters beyond the designated zone indicates a lack of precision in landing. Furthermore, the runway touchdown position being 9.6 meters off the centerline is a concern as it suggests a lack of alignment with the runway.
The warning about landing with a 13 knot tailwind is particularly concerning as it goes against safe landing practices. Tailwind landings can significantly increase the risks associated with landing and should be avoided whenever possible.
Lastly, in the Rollout Phase, the runway alignment being 9.4 meters off the centerline highlights the need for improved alignment and control during the rollout process. Proper alignment is crucial for ensuring a safe and efficient exit from the runway.
Overall, while the aircraft landing score of 83.6% is not ideal, it provides valuable feedback for areas of improvement. By addressing issues such as descent path, threshold height, landing flare, touchdown rate, alignment, and tailwind landings, pilots can work towards achieving safer and more precise landings in the future. Remember, continuous learning and improvement are key to maintaining high standards in aviation safety.
Scroll or drag the slider to zoom · double-click to reset · hover for values