Events
Events
Events
Events
Events
Events
Events
MY FS FLIGHTS
Flight Score
Departure
Apply small rudder corrections against a point at the far end of the runway to hold the centreline during the roll.
What happened: The aircraft tracked 78 ft off the runway centreline during the ground roll, and flights with this pattern usually carry extra bank, around 2°, into the first climb.
Watch for: Heading indicator: wings level, tracking the runway centreline
Arrival
Raise the nose more slowly in the flare and stop as soon as the sink is checked; if it balloons, hold the attitude.
What happened: The flare ballooned, with 376 fpm of sink returning after the arrest; a balloon like this usually carries through to a firm touchdown, as it did here at 327 fpm.
Watch for: The runway ahead: the aircraft still sinking gently towards it through the flare, never rising.
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.
One stabilised approach gate: seven 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.
At the 500 ft gate: sink rate above what the glideslope needed, off the runway's 3° glideslope and off the centreline.
The approach, gate by gate
Side view — the last 5,488 ft of the approach.
Plan view — the first 5,488 ft of the 7,988 ft runway, to the same scale as the side view.
Touched down 3,375 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 12 minutes and covered a distance of 2 nautical miles. The aircraft, an Airbus A321, then departed from runway 28R at San Francisco International Airport (KSFO). The takeoff distance was 2,833 feet, which is 25% of the runway length. The liftoff speed was 152 knots.
As the aircraft climbed out of KSFO, it began its enroute climb, which started overhead the airport. The climb took 25 minutes and covered a distance of 157 nautical miles, with the aircraft ascending from 1,007 feet above sea level to 37,839 feet above sea level, an increase of 36,832 feet. The enroute climb took the aircraft over the Flying N Ranch Airport (CA04) in California, and it leveled off at 37,839 feet.
The enroute level cruise lasted for 27 minutes and covered a distance of 206 nautical miles. The aircraft was cruising 6 miles southwest of the Flying N Ranch Airport. After the cruise, the aircraft began its enroute descent, which started 5 miles east of Culp Creek in Oregon. The descent took 23 minutes and covered a distance of 112 nautical miles, with the aircraft descending from 37,725 feet above sea level to 1,786 feet above sea level, a decrease of 35,939 feet.
The final approach to runway 28R at Portland International Airport (KPDX) was made from the southeast, with a heading of 295.0 degrees. The aircraft was at an altitude of 1,746 feet above ground level and 2 nautical miles from the runway. The landing was made on runway 28R, which has a length of 7,988 feet. The threshold height was well above the target, and the threshold speed was also well above the target at 152 knots.
The touchdown point was 1,993 feet beyond the touchdown zone, and the touchdown speed was 137 knots, which was a little fast. The touchdown rate was firm at -371 feet per minute. The runway touchdown position was misaligned by 31 feet from the centerline. The local weather at the time of landing was 84 degrees Fahrenheit.
The total landing distance was 5,198 feet, which is 65% of the runway length. The runway rollout alignment was significantly misaligned by 126 feet from the centerline. After landing, the aircraft taxied to the parking, which took 2 minutes and covered a distance of less than 1 nautical mile. The total flight distance was 481 nautical miles, and the flight took 87 minutes. The aircraft used 8,633 pounds of fuel during the flight.
The Airbus A321 aircraft has successfully landed at Portland International Airport (KPDX) on runway 28R. However, the landing was not without some issues. The final approach was initiated from the southeast, heading 295.0° at 2 nautical miles and 1,746 feet above ground level (agl).
Upon landing, the aircraft touched down 1,993 feet beyond the touchdown zone, which is a significant deviation from the target. The touchdown speed of 137 knots was also a little fast, indicating that the pilot may have been unable to fully arrest the aircraft's descent before touchdown. The touchdown rate of -371 feet per minute (fpm) was firm, suggesting that the aircraft's wheels made contact with the runway with a moderate amount of force.
One of the most notable issues with this landing was the misalignment of the runway touchdown position. The aircraft was 31 feet off-centerline, which could have been due to a variety of factors, including pilot error or issues with the aircraft's navigation systems. Additionally, the runway rollout alignment was significantly misaligned by 126 feet from centerline, which could have made it more difficult for the pilot to control the aircraft during the rollout phase.
The threshold height at 79 feet agl was well above the target, and the threshold speed of 152 knots was also well above the target. This suggests that the pilot may have been unable to fully configure the aircraft for landing, which could have contributed to the issues with the touchdown and rollout phases.
The local weather conditions at the time of the landing were warm, with a temperature of 84°F. This may have contributed to some of the issues with the landing, as warm air can be more turbulent and difficult to navigate.
Overall, while the Airbus A321 aircraft was able to land safely at KPDX, the landing was not without some issues. The pilot will need to review the flight data and make adjustments to improve the accuracy and safety of future landings.
Scroll or drag the slider to zoom · double-click to reset · hover for values