Events
Events
Events
Events
Events
Events
MY FS FLIGHTS
Flight Score
Shorten the long landing
Ground effect becomes significant below about one wingspan of height. A Cessna 172, with a 36 ft span, enters ground effect at flare height - the float it feels in the hold-off is ground effect arriving on cue. An A320, with a span around 117 ft, has been in ground effect since before the threshold and there is no sudden cushion to feel, only a gradual reduction in induced drag that lengthens any float you allow.
Read more in Flare TimingStart to finish · 19 stages, 17 scored
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 7,507 ft of the approach.
Plan view — the first 7,507 ft of the 9,425 ft runway, to the same scale as the side view.
Touched down 4,789 ft 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 5 minutes and covered less than 1 nautical mile. The aircraft, a Boeing 737-700, then departed from runway 24L at KCLE Cleveland Hopkins International Airport. The takeoff distance was 4,113 feet, which accounted for 51% of the runway. The liftoff speed was 155 knots.
The local weather conditions at the time of departure were characterized by a temperature of 46°F and a wind speed of 5 knots from a direction of 310°. The crosswind component was 4 knots, while the headwind component was 1 knot. As the aircraft took off, it began its enroute climb, which started overhead KCLE Cleveland Hopkins International Airport. The climb took the aircraft from an altitude of 1,775 feet above sea level to 28,872 feet above sea level, an increase of 27,097 feet in 13 minutes, covering a distance of 67 nautical miles.
Following the enroute climb, the aircraft entered a level cruise phase, which started 4 miles west of Amsterdam, Ohio. This phase lasted for 14 minutes and covered a distance of 99 nautical miles. The aircraft then began its enroute descent, which started 2 miles southeast of Grantsville, Maryland. The descent took the aircraft from an altitude of 28,779 feet above sea level to 2,227 feet above sea level, a decrease of 26,552 feet in 21 minutes, covering a distance of 100 nautical miles.
The enroute descent phase was followed by another level cruise phase, which started overhead MD46 Glenair Airport Dayton, Maryland. This phase lasted for 5 minutes and covered a distance of 13 nautical miles. The aircraft then began its final approach to runway 10 at KBWI Baltimore/Washington International Thurgood Marshall Airport, approaching from the west at a heading of 94.0°. The aircraft was at an altitude of 1,321 feet above ground level and 4 nautical miles from the runway.
The landing on runway 10 at KBWI Baltimore/Washington International Thurgood Marshall Airport was characterized by a runway length of 9,425 feet. The threshold height was above the target, while the threshold speed was well above the target at 151 knots. The touchdown point was very long, using more than 50% of the available runway. The touchdown speed was 126 knots, which was a little fast, while the touchdown rate was fair at -236 feet per minute. The runway touchdown position was slightly misaligned by 18 feet from the centreline.
The local weather conditions at the time of landing were characterized by a temperature of 72°F and a wind speed of 9 knots from a direction of 342°. The crosswind component was 8 knots, while the tailwind component was 3 knots. The total landing distance was 7,239 feet, which accounted for 77% of the runway. The runway rollout alignment was slightly misaligned by 35 feet from the centreline. The taxiing period from the runway to the parking took 4 minutes and covered less than 1 nautical mile.
The total flight distance was 286 nautical miles, which was covered in 64 minutes. The aircraft used 5,757 pounds of fuel during the flight.
The Boeing 737-700 aircraft successfully landed at KBWI Baltimore/Washington International Thurgood Marshall Airport, but the landing was not without some notable issues. The final approach to runway 10 from the west was executed at a heading of 94.0°, with the aircraft at 4 nautical miles and 1,321 feet above ground level (agl). The landing was scored at 81.7%, indicating a decent but not outstanding performance.
One of the notable issues with the landing was the threshold height, which was above the target at 69 feet agl. This suggests that the aircraft may have been slightly high on its approach, which could have contributed to the subsequent issues. The threshold speed was also well above the target at 151 knots, which is a concern as it may indicate that the aircraft was not properly configured for landing.
The touchdown point was very long, using more than 50% of the available runway. This suggests that the aircraft may have been slightly too fast or not properly configured for landing, leading to a longer than necessary rollout. The touchdown speed of 126 knots was also a little fast, which could have contributed to the long touchdown point. The touchdown rate of -236 feet per minute (fpm) was fair, but not outstanding.
The runway touchdown position was slightly misaligned by 18 feet from the centreline, which could have made the landing more challenging. The local weather conditions were relatively calm, with a temperature of 72°F and winds of 9 knots at 342°. The crosswind was 8 knots, while the tailwind was 3 knots, which may have contributed to the slight misalignment.
The total landing distance was 7,239 feet, which is 77% of the available runway. This suggests that the aircraft was able to stop safely, but the long touchdown point and rollout may have been a concern. The runway rollout alignment was also slightly misaligned by 35 feet from the centreline, which could have made the landing more challenging.
Overall, while the landing was not perfect, the aircraft was able to stop safely and the pilot was able to recover from the issues. However, there are areas for improvement, particularly in terms of configuring the aircraft for landing and maintaining a proper approach speed.
Scroll or drag the slider to zoom · double-click to reset · hover for values