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
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.
The approach, gate by gate
Side view — the last 1,524 m of the approach.
Plan view — the first 1,524 m of the 2,562 m runway, to the same scale as the side view.
Touched down 585 m past the threshold — beyond the full-score zone. The arrival was smooth.
The rest of the report
The flight began with the Airbus A320 taxiing from the parking area to the runway at Phoenix Sky Harbor International Airport, taking 12 minutes and covering a distance of 3 nautical miles. The departure roll took place on runway 25R, with the aircraft lifting off at a speed of 168 knots after covering 71% of the runway's length.
As the aircraft climbed to its cruising altitude, it passed over Central City in Arizona, increasing its altitude from 2,095 feet to 35,462 feet in 23 minutes and covering a distance of 153 nautical miles. The enroute climb was a significant portion of the flight, marking the beginning of the aircraft's ascent to its cruising altitude.
Once the aircraft reached its cruising altitude, it entered a level cruise phase, which lasted for 173 minutes and covered a distance of 1,453 nautical miles. This phase of the flight took place 10 miles east of Bowie, Arizona, and was a critical part of the journey, allowing the aircraft to maintain a steady altitude and speed.
As the aircraft approached its destination, it began its descent, starting 2 miles west of Pine Island Center in Florida. The descent from 35,753 feet to 3,210 feet took 23 minutes and covered a distance of 131 nautical miles. The aircraft then entered another level cruise phase, this time lasting only 5 minutes and covering 12 nautical miles, before beginning its final descent.
The final descent took place 4 miles east of Key Biscayne, Florida, and lasted only 3 minutes, during which the aircraft descended from 2,945 feet to 1,298 feet. The aircraft then began its final approach to runway 30 at Miami International Airport, flying from the southeast and heading 300.0 degrees at an altitude of 1,279 feet.
The landing took place on runway 30, which was 2,562 meters long. The threshold height was good, but the threshold speed was slightly above the target speed of 139 knots. The touchdown point was 168 meters beyond the touchdown zone, and the touchdown speed was 129 knots, which was a little fast. However, the touchdown rate was firm at -305 feet per minute, and the runway touchdown alignment was perfect.
After landing, the aircraft taxied to the parking area, taking 4 minutes and covering a distance of less than 1 nautical mile. The total flight distance was 1,766 nautical miles, and the flight lasted for 243 minutes. The aircraft used 9,586 kilograms of fuel during the flight.
The Airbus A320 successfully landed at Miami International Airport (KMIA) on runway 30, achieving a score of 97.7%. The aircraft approached the runway from the southeast, heading 300.0° at a distance of 4 nautical miles and an altitude of 1,279 feet above ground level (agl). The final approach was executed with precision, and the aircraft landed on the runway with a threshold height that met the required standards.
However, there were a few areas where the landing could be improved. The threshold speed was slightly above the target speed of 138 kt, coming in at 139 kt. Additionally, the touchdown speed of 129 kt was a bit faster than desired, indicating that the aircraft could have been slowed down more effectively during the approach. The touchdown rate of -305 fpm was firm, but this could be a concern if the aircraft was carrying a heavy load or if the runway surface was slippery.
Despite these minor issues, the landing was otherwise successful. The runway touchdown alignment was perfect, indicating that the aircraft was aligned with the runway centerline at the moment of touchdown. The local weather conditions were also favorable, with a temperature of 12°C and a headwind of 11 kt at 310°. The crosswind component was minimal, at just 2 kt, which made the landing even more manageable.
The total landing distance of 1,232 meters was 48% of the runway length, which is a relatively short distance considering the aircraft's size and weight. The runway rollout alignment was also perfect, indicating that the aircraft was able to maintain its alignment with the runway centerline even after touchdown. Overall, the landing was a success, and with a few minor adjustments, the aircraft could have achieved an even higher score.
Scroll or drag the slider to zoom · double-click to reset · hover for values