Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
MY FS FLIGHTS
Flight Score
Configure earlier
See Arrival Final 3
Preparing for a stable approach will give you time to decide on whether to attempt the landing or going around. Too much altitude with a high sink rate will result in carrying too much speed onto the runway. Configuring flaps and the gear late also won't help the speed decay.
Read more in The Stabilised ApproachStart to finish · 21 stages, 19 in the score
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.
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: off the centreline and wings not level.
At the 500 ft gate: off the centreline.
The approach, gate by gate
Side view — the last 1,524 m of the approach.
Plan view — the first 1,524 m of the 1,611 m runway, to the same scale as the side view.
Touched down 521 m past the threshold — beyond the full-score zone. The arrival was smooth.
The rest of the report
The flight began with the aircraft taxiing from the parking area to the runway, a process that took 7 minutes and covered a distance of 3 nautical miles. The Airbus A320 then departed from runway 19R at Kansas City International Airport (KMCI), with a takeoff distance of 1,548 meters, which accounted for 47% of the runway. The aircraft lifted off at a speed of 154 knots.
As the aircraft climbed to its cruising altitude, it encountered local weather conditions of 9°C temperature and a wind speed of 5 knots at 250°. The crosswind was 4 knots, while the headwind was 3 knots. The enroute climb started overhead KMCI, with the aircraft ascending from 2,016 feet above sea level to 35,398 feet above sea level, an increase of 33,382 feet in 18 minutes, covering a distance of 115 nautical miles.
After reaching its cruising altitude, the aircraft entered a level cruise, which started 4 miles west of Brashear, Missouri, and lasted for 5 minutes, covering a distance of 44 nautical miles. The aircraft then began its descent, starting 3 miles west of Warsaw, Illinois, and descending from 35,324 feet above sea level to 6,119 feet above sea level, a decrease of 29,205 feet in 25 minutes, covering a distance of 160 nautical miles.
The aircraft entered another level cruise, this time starting 1 mile southwest of 84IL Rossi's Farm Airport in Minooka, Illinois, and lasting for 2 minutes, covering a distance of 8 nautical miles. The descent then started 2 miles northwest of Crest Hill, Illinois, and the aircraft descended from 5,970 feet above sea level to 4,245 feet above sea level, a decrease of 1,725 feet in 3 minutes, covering a distance of 16 nautical miles.
The aircraft entered another level cruise, starting overhead Hickory Hills, Illinois, and lasting for 2 minutes, covering a distance of 6 nautical miles. The descent then started 1 mile southeast of Chicago Lawn, Illinois, and the aircraft descended from 3,961 feet above sea level to 1,474 feet above sea level, a decrease of 2,487 feet in 3 minutes, covering a distance of 4 nautical miles.
The final approach to runway 22L at Chicago Midway International Airport (KMDW) was made from the northeast, heading 220.0° at 3 nautical miles and 857 feet above ground level. The aircraft landed on the runway, with a touchdown point 99 meters beyond the touchdown zone. The touchdown speed was 122 knots, which was good, but the touchdown rate was hard at -405 feet per minute.
The total landing distance was 1,329 meters, which accounted for 82% of the runway. The runway rollout alignment was very good. The aircraft then taxiied to the parking area from the runway, a process that took 3 minutes and covered a distance of less than 1 nautical mile. The total flight distance was 363 nautical miles, taking 71 minutes, and the aircraft used 2,592 kilograms of fuel.
The Airbus A320 successfully landed on runway 22L at KMDW Chicago Midway International Airport, achieving a score of 90.8%. The aircraft approached the runway from the north east, heading 220.0° at 3 nautical miles and 857 feet above ground level (agl). The pilot maintained a good threshold height, which is a crucial aspect of a safe landing.
Upon touchdown, the aircraft's threshold speed was recorded at 136 knots, which is within the acceptable range. The touchdown point was 99 meters beyond the touchdown zone, indicating a slight deviation from the ideal landing spot. However, the touchdown speed of 122 knots was good, suggesting that the pilot maintained control of the aircraft during the landing process.
The touchdown rate of -405 feet per minute (fpm) was considered hard, which may indicate that the pilot could have applied a smoother touchdown. Nevertheless, the runway touchdown position was slightly misaligned by 7.0 meters from the centerline, but the rollout alignment was very good.
The local weather conditions at the time of landing were characterized by a temperature of 7°C and a wind speed of 8 knots at 290°. The crosswind component was 7 knots, while the headwind component was 3 knots. These conditions did not appear to significantly impact the landing, as the pilot was able to maintain control of the aircraft.
The total landing distance of 1,329 meters was 82% of the runway length, which is a relatively short distance. This suggests that the pilot was able to bring the aircraft to a stop quickly and efficiently, despite the hard touchdown rate. Overall, the landing was considered successful, with the pilot demonstrating good control and management of the aircraft during the approach and landing phases.
Scroll or drag the slider to zoom · double-click to reset · hover for values