Events
Events
Events
Events
Events
Events
Events
Events
Events
MY FS FLIGHTS
Flight Score
Work on the flare
See Arrival Landing
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 · 26 stages, 24 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.
Two stabilised approach gates, each with seven checks, where the approach path is 1,000 ft and 500 ft above the runway.
At the 1,000 ft gate: speed above the reference speed.
At the 500 ft gate: speed above the reference speed.
The approach, gate by gate
Side view — the last 2,087 m of the approach.
Plan view — the first 2,087 m of the 2,512 m runway, to the same scale as the side view.
Touched down 916 m past the threshold — beyond the full-score zone. The arrival was smooth.
The rest of the report
The flight began with a taxiing period from the parking to the runway, which took 6 minutes and covered less than 1 nautical mile. The aircraft, an Airbus A321, then departed from runway 21 at Eindhoven Airport (EHEH). The takeoff distance was 1,561 meters, which accounted for 62% of the runway. The liftoff speed was 156 knots.
The local weather conditions at the time of takeoff were characterized by a temperature of 22°C and a wind speed of 14 knots from a direction of 270°. This resulted in a crosswind of 11 knots and a headwind of 8 knots. The aircraft began its enroute climb overhead Oerle, a town in the province of North Brabant, the Netherlands. The climb started from an altitude of 1,081 feet above sea level and reached 7,002 feet in just 3 minutes, covering a distance of 6 nautical miles.
As the aircraft continued its journey, it began its enroute descent overhead Valkenswaard, another town in the province of North Brabant. The descent started from an altitude of 7,119 feet and ended at 3,229 feet, a decrease of 3,889 feet in 5 minutes, covering a distance of 5 nautical miles. The aircraft then entered a level cruise, starting 1 mile south east of Bergeyk and lasting 7 minutes, covering a distance of 12 nautical miles.
The enroute descent continued overhead Batadorp, where the aircraft descended from 3,145 feet to 1,998 feet in 2 minutes, covering a distance of 6 nautical miles. The level cruise resumed 1 mile south west of Zijtaart and lasted 5 minutes, covering a distance of 5 nautical miles. The final approach to runway 21 at Eindhoven Airport was made from the north east, heading 215.0° at an altitude of 1,265 feet above ground level and a distance of 4 nautical miles.
However, the aircraft was required to perform a go-around at an altitude of 9 feet above ground level. The landing was eventually made on runway 21, with a touchdown point 522 meters beyond the touchdown zone. The touchdown speed was 182 knots, which was excessively fast, while the threshold speed was 196 knots, which was also excessively high. The touchdown rate was smooth at -105 feet per minute, and the runway touchdown alignment was very good.
The local weather conditions at the time of landing were characterized by a temperature of 17°C and a wind speed of 8 knots from a direction of 250°. This resulted in a crosswind of 5 knots and a headwind of 7 knots. The total landing distance was 2,028 meters, which accounted for 81% of the runway. The runway rollout alignment was perfect, and the taxiing to the parking from the runway took 6 minutes, covering a distance of 1 nautical mile.
The total flight distance was 51 nautical miles, taking 46 minutes, and the aircraft used 2,025 kilograms of fuel.
First and foremost, let me acknowledge the strong points of the aircraft landing score. The Approach Phase performance was commendable with excellent glideslope alignment, which is crucial for a safe and efficient landing. Additionally, the threshold speed was maintained at a relatively high 196 kt, ensuring the aircraft was well-prepared for touchdown.
Moving on to the Landing Phase, the threshold height was well-handled, indicating proper altitude management during descent. However, it is important to address the fact that the landing flare was identified as very poor. The landing flare is a critical aspect of a successful landing as it helps to reduce touchdown speed and ensure a smooth landing transition. Improving this aspect of the landing technique can greatly enhance the overall performance.
In the Touchdown Phase, it is worth noting that the touchdown rate was smooth at -105 ft/m, indicating a relatively gentle touchdown. However, the touchdown speed of 182 kt was identified as excessively fast. Landing at such high speeds can compromise safety and increase wear and tear on the aircraft. Additionally, the touchdown point being 522 m beyond the touchdown zone is a significant concern, as it indicates a failure to accurately judge the touchdown point on the runway. Correcting these factors will be crucial in improving future landings.
On a positive note, the runway touchdown alignment was identified as very good, which is essential for safe and efficient landings. This aspect of the landing was well-executed, contributing to the overall score.
In conclusion, while there were some positive aspects of the aircraft landing score, such as the excellent glideslope alignment and good threshold height, there are clear areas for improvement. Focusing on enhancing the landing flare technique, reducing touchdown speed, and improving judgment of the touchdown point will lead to a more successful and safe landing in future flights. Keep up the good work, and continue to strive for excellence in all aspects of aircraft operation.
Scroll or drag the slider to zoom · double-click to reset · hover for values