Events
Events
Events
Events
Events
Events
Events
MY FS FLIGHTS
Flight Score
Departure
Make small rudder corrections against a point at the far end to hold the centreline.
What happened: During the ground roll you drifted 8.3 m off the runway centreline.
Watch for: Watch runway alignment against the centreline, correcting with small rudder inputs.
See Departure Roll
Arrival
Begin the flare with progressive back pressure and keep it coming until the sink is arrested, rather than flying it on flat.
What happened: The nose was barely raised in the flare and little of the sink was taken out, flying the aircraft onto the runway. This pattern usually carries through to a firm touchdown with a noticeable sink rate.
Watch for: Vertical speed indicator: a smoothly reducing sink through the normal flare band, not a steady rate into the runway.
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 · 18 stages, 16 scored
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,738 m runway, to the same scale as the side view.
The 320 m touchdown sits inside 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 Ronald Reagan Washington National Airport, taking approximately 9 minutes to cover a distance of 1 nautical mile. The departure roll took place on runway 33, with the aircraft lifting off at a speed of 150 knots after covering 83% of the runway's length, which was 1,316 meters.
As the aircraft took to the skies, it encountered local weather conditions of 8 degrees Celsius and a wind speed of 26 knots at 310 degrees. The crosswind was 6 knots, while the headwind was 26 knots. The enroute climb began approximately 1 mile southwest of Washington, with the aircraft ascending from an altitude of 1,175 feet above sea level to 34,012 feet above sea level, an increase of 32,838 feet, in 19 minutes and covering a distance of 120 nautical miles.
Following the climb, the aircraft entered a level cruise phase, which started 4 miles north of the Flatwoods Airport in Lovingston, Virginia. This phase lasted for 32 minutes and covered a distance of 236 nautical miles. The enroute descent began 6 miles southeast of the Brevard Airport in Brevard, North Carolina, with the aircraft descending from an altitude of 33,984 feet above sea level to 2,383 feet above sea level, a decrease of 31,601 feet, in 25 minutes and covering a distance of 133 nautical miles.
The final approach to runway 26R at Hartsfield Jackson Atlanta International Airport was made from the east, with the aircraft heading at 270 degrees at an altitude of 1,357 feet above ground level and a distance of 4 nautical miles from the runway. The landing took place on the runway, which was 2,738 meters long, with a good threshold height. The threshold speed was also good at 141 knots, but the touchdown speed was a little fast at 139 knots, resulting in a heavy touchdown rate of -640 feet per minute. The runway touchdown position was slightly misaligned from the centreline by 3.2 meters.
The total landing distance was 1,398 meters, which was 51% of the runway's length. The runway rollout alignment was also misaligned from the centreline by 15.8 meters. Taxiing to the parking area from the runway took approximately 4 minutes and covered a distance of less than 1 nautical mile. The total flight distance was 496 nautical miles, taking a total of 90 minutes, and the aircraft used 3,518 kilograms of fuel during the flight.
The Airbus A320 successfully landed on runway 26R at KATL Hartsfield Jackson Atlanta International Airport, achieving a score of 89.3%. The aircraft approached the runway from the east, heading 270.0° at a distance of 4 nautical miles and an altitude of 1,357 feet above ground level (agl).
The landing was executed with a good threshold height, indicating that the aircraft was at the correct altitude as it touched down on the runway. The threshold speed of 141 knots was also within the acceptable range, demonstrating the pilot's ability to control the aircraft's speed during the final approach. However, the touchdown speed of 139 knots was slightly faster than desired, which may have contributed to the heavy touchdown rate of -640 feet per minute (fpm).
The touchdown distance of 321 meters was within the acceptable range, but the runway touchdown position was slightly misaligned by 3.2 meters from the centerline. This misalignment may have been due to the crosswind, which was 23 knots, or the headwind, which was 8 knots. The local weather conditions, with a temperature of 4°C and a wind speed of 24 knots at 340°, may have also played a role in the misalignment.
The total landing distance of 1,398 meters was 51% of the runway length, which is within the acceptable range. However, the runway rollout alignment was misaligned by 15.8 meters from the centerline, indicating that the aircraft may have drifted off the centerline during the rollout phase.
Overall, the landing was successful, but there were some areas for improvement, particularly in terms of touchdown speed and runway alignment. The pilots demonstrated good control of the aircraft during the final approach and touchdown, but may need to work on maintaining a more precise alignment during the rollout phase.
Scroll or drag the slider to zoom · double-click to reset · hover for values