Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
MY FS FLIGHTS
Flight Score
Arrival
Hold the aim point and wait for the speed to bleed before raising the nose, starting the flare within the normal band instead of 93 ft.
What happened: The flare began at 93 ft, 48 ft earlier than the normal band.
Watch for: Radio altimeter: start the flare within the normal flare band
See Arrival Landing
Twenty knots on a monitor produces the visual sensation of about ten. The advice to "taxi at a walking pace" cannot fix this, because your sense of walking pace is exactly the thing that's broken. Put the groundspeed readout in your scan and obey it for the next fifty flights, the way a student pilot leans on the airspeed indicator before learning to read attitude.
Read more in How to Taxi AnywhereStart to finish · 20 stages, 18 scored
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.
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,246 m runway, to the same scale as the side view.
The 84 m touchdown sits inside 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 10 minutes and covered a distance of 4 nautical miles. The aircraft, a Boeing 737-800, then departed from runway 36L at EHAM Amsterdam Airport Schiphol. The takeoff distance was 1,252 meters, which was 35% of the runway length. The liftoff speed was 158 knots.
The local weather conditions at the time of departure were characterized by a temperature of -1°C, with a wind speed of 2 knots at 139°. The crosswind was 1 knot, and the tailwind was also 1 knot. After a successful takeoff, the aircraft began its enroute climb, starting 1 mile southwest of Halfweg, a location in the province of Noord-Holland, the Netherlands. The climb took 20 minutes and covered a distance of 106 nautical miles, during which the aircraft ascended from 1,022 feet above sea level to 32,017 feet above sea level, an increase of 30,995 feet.
Following the enroute climb, the aircraft entered a level cruise phase, which started 25 miles southeast of Orford, a location in Suffolk, England. This phase lasted for 194 minutes and covered a distance of 1,374 nautical miles. The aircraft then began its enroute descent, starting 57 miles east of Agua Retorta, a location in the Azores, Portugal. The descent took 18 minutes and covered a distance of 89 nautical miles, during which the aircraft descended from 32,221 feet above sea level to 4,257 feet above sea level, a decrease of 27,964 feet.
The aircraft then entered another level cruise phase, which started 6 miles southwest of Relva, a location in the Azores, Portugal. This phase lasted for 35 minutes and covered a distance of 17 nautical miles. The aircraft then began its final descent, starting 3 miles south of Ribeira Cha, a location in the Azores, Portugal. The descent took 2 minutes and covered a distance of 8 nautical miles, during which the aircraft descended from 3,835 feet above sea level to 1,502 feet above sea level, a decrease of 2,333 feet.
The final approach to runway 30 at LPPD João Paulo II Airport was made from the east, with a heading of 291.0° at 4 nautical miles and 1,280 feet above ground level. The landing was successful, with a touchdown speed of 124 knots and a touchdown rate of -52 feet per minute. The touchdown distance was 82 meters, and the runway touchdown position was misaligned by 8.2 meters from the centerline. The local weather conditions at the time of landing were characterized by a temperature of 17°C, with a wind speed of 13 knots at 219°. The crosswind was 12 knots, and the headwind was 4 knots.
The total landing distance was 1,131 meters, which was 50% of the runway length. The runway rollout alignment was slightly misaligned by 10.5 meters from the centerline. The taxiing period from the runway to the parking took 2 minutes and covered a distance of less than 1 nautical mile. The total flight distance was 1,604 nautical miles, and the flight duration was 284 minutes. The aircraft used 12,622 kilograms of fuel during the flight.
The Boeing 737-800 aircraft successfully landed at LPPD João Paulo II Airport, achieving a score of 95.6%. The final approach to runway 30 was conducted from the east, heading 291.0° at a distance of 4 nautical miles and an altitude of 1,280 feet above ground level (agl). The aircraft touched down on the runway, which has a length of 2,246 meters, with a good threshold height.
The threshold speed was slightly below the target speed of 131 knots, but the touchdown distance of 82 meters was considered good. The touchdown speed of 124 knots was also within acceptable limits, and the touchdown rate of -52 feet per minute (fpm) was excellent. However, the runway touchdown position was misaligned by 8.2 meters from the centerline, which may have been due to factors such as wind or pilot error.
The local weather conditions at the time of landing were characterized by a temperature of 17°C and a wind speed of 13 knots from 219°. The crosswind component was 12 knots, while the headwind component was 4 knots. These conditions may have contributed to the slight misalignment of the runway touchdown position.
The total landing distance of 1,131 meters was 50% of the runway length, which is a relatively short distance. However, the runway rollout alignment was slightly misaligned by 10.5 meters from the centerline, which may indicate some issues with the aircraft's braking or steering performance.
Overall, the landing was considered successful, with the aircraft achieving a good touchdown speed and distance. However, there were some minor issues with the runway touchdown position and rollout alignment, which may require further investigation and improvement.
Scroll or drag the slider to zoom · double-click to reset · hover for values