Events
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 · 21 stages, 19 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.
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 5,746 ft of the approach.
Plan view — the first 5,746 ft of the 9,425 ft runway, to the same scale as the side view.
Touched down 2,037 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 9 minutes and covered a distance of 3 nautical miles. The aircraft, a Boeing 737-700, then departed from runway 04 at KROC Frederick Douglass Greater Rochester International Airport. The takeoff distance was 3,686 feet, which accounted for 59% of the runway. The liftoff speed was 148 knots.
The local weather conditions at the time of departure were characterized by a temperature of 40°F, with a wind speed of 4 knots from a direction of 280°. This resulted in a crosswind of 3 knots and a tailwind of 1 knot. The aircraft then began its enroute climb, starting overhead the airport and rising from an altitude of 1,560 feet above sea level to 29,275 feet above sea level, an increase of 27,715 feet in 12 minutes and covering a distance of 47 nautical miles.
Following the initial climb, the aircraft entered a level cruise, starting 4 miles west of Almond, New York, and lasting for 20 minutes. During this period, the aircraft covered a distance of 151 nautical miles. The aircraft then began its enroute descent, starting 1 mile west of PA08 JJ, and descending from 29,221 feet above sea level to 3,005 feet above sea level, a decrease of 26,216 feet in 14 minutes and covering a distance of 59 nautical miles.
The aircraft then entered another level cruise, starting 2 miles northeast of Lutherville-Timonium, Maryland, and lasting for 2 minutes. It covered a distance of 6 nautical miles during this period. The aircraft then began its final descent, starting overhead Perry Hall, Maryland, and descending from 3,008 feet above sea level to 2,319 feet above sea level, a decrease of 689 feet in 2 minutes and covering a distance of 5 nautical miles.
The aircraft then entered another level cruise, starting 1 mile northwest of Bowleys Quarters, Maryland, and lasting for 6 minutes. It covered a distance of 13 nautical miles during this period. The aircraft then began its final approach to runway 28 at KBWI Baltimore/Washington International Thurgood Marshall Airport, approaching from the east and heading 274.0° at a distance of 4 nautical miles and an altitude of 1,267 feet above ground level.
The landing on runway 28 was successful, with the aircraft touching down 660 feet beyond the touchdown zone. The touchdown speed was 130 knots, which was a little fast, and the touchdown rate was fair at -236 feet per minute. The runway touchdown position was slightly misaligned by 11 feet from the centerline. The local weather conditions at the time of landing were characterized by a temperature of 59°F, with a wind speed of 3 knots from a direction of 310°. This resulted in a crosswind of 2 knots and a headwind of 2 knots.
The total landing distance was 5,469 feet, which accounted for 58% of the runway. The runway rollout alignment was very good. The taxiing period from the runway to the parking took 4 minutes and covered a distance of less than 1 nautical mile. The total flight distance was 290 nautical miles, and the flight duration was 72 minutes. The aircraft used 6,119 pounds of fuel during the flight.
The Boeing 737-700 aircraft successfully landed at KBWI Baltimore/Washington International Thurgood Marshall Airport, achieving a score of 89.4%. The final approach to runway 28 was initiated from the east, with a heading of 274.0° at a distance of 4 nautical miles and an altitude of 1,267 feet above ground level (agl).
Upon landing, the aircraft touched down 660 feet beyond the designated touchdown zone, which is slightly off-target. The touchdown speed of 130 knots was a bit faster than the target speed, indicating that the pilot may have been able to flare the aircraft more effectively to reduce the touchdown speed. The touchdown rate of -236 feet per minute (fpm) was considered fair, suggesting that the pilot maintained a relatively smooth descent.
The runway touchdown position was slightly misaligned by 11 feet from the centerline, which may have been due to a slight deviation in the approach or a minor issue with the aircraft's alignment during the landing roll. However, the runway rollout alignment was very good, indicating that the pilot maintained control of the aircraft during the landing roll and was able to align the aircraft with the runway centerline.
The local weather conditions at the time of the landing were relatively calm, with a temperature of 59°F and a wind speed of 3 knots from 310°. The crosswind and headwind components were both 2 knots, which is relatively minimal and would not have significantly impacted the landing. The total landing distance of 5,469 feet was 58% of the available runway length, which is a reasonable distance considering the aircraft's size and weight.
Overall, the landing was considered successful, with the pilot demonstrating good control and management of the aircraft during the approach and landing phases. However, there were some minor issues with the touchdown point and touchdown speed, which may be addressed in future training or evaluation exercises.
Scroll or drag the slider to zoom · double-click to reset · hover for values