Events
Events
Events
Events
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 · 22 stages, 20 scored
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
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 2,035 m of the approach.
Plan view — the first 2,035 m of the 3,516 m runway, to the same scale as the side view.
Touched down 662 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 8 minutes and covered a distance of 3 nautical miles. The Airbus A321 then departed from runway 28L at Portland International Airport, with a takeoff distance of 888 meters, which accounted for 27% of the runway. The aircraft lifted off at a speed of 138 knots.
As the flight progressed, the aircraft climbed from an altitude of 1,029 feet above sea level to 33,316 feet, an increase of 32,287 feet, in 16 minutes and covering a distance of 72 nautical miles. The enroute climb started 1 mile east of Bridgeton, Oregon, and the aircraft continued to climb until it reached the desired altitude.
Following the climb, the aircraft entered a level cruise phase, which started 3 miles north of Halsey, Oregon, and lasted for 52 minutes, covering a distance of 340 nautical miles. The aircraft then began its descent from 34,078 feet above sea level to 9,066 feet, a decrease of 25,013 feet, in 16 minutes and covering a distance of 88 nautical miles. This descent started 1 mile northwest of Middletown, California.
The aircraft then entered another level cruise phase, which started 7 miles southeast of Meadowlark Field in Livermore, California, and lasted for 2 minutes, covering a distance of 5 nautical miles. The aircraft then began its descent from 8,852 feet above sea level to 5,205 feet, a decrease of 3,647 feet, in 3 minutes and covering a distance of 10 nautical miles. This descent started 6 miles east of Sunol, California.
The aircraft then entered another level cruise phase, which started overhead Fremont, California, and lasted for 2 minutes, covering a distance of 5 nautical miles. The aircraft then began its descent from 4,694 feet above sea level to 1,284 feet, a decrease of 3,410 feet, in 5 minutes and covering a distance of 11 nautical miles. This descent started 2 miles west of Newark, California.
The final approach to runway 28R at San Francisco International Airport was made from the southeast, heading 298.0 degrees at 4 nautical miles and 1,262 feet above ground level. The aircraft landed on the runway, with a touchdown point 244 meters beyond the touchdown zone. The touchdown speed was 122 knots, which was good, and the touchdown rate was firm at -300 feet per minute.
The local weather conditions at the time of landing were a temperature of 13 degrees Celsius, with a wind speed of 25 knots from 180 degrees. The crosswind was 22 knots, and the tailwind was 12 knots. The total landing distance was 1,953 meters, which accounted for 56% of the runway. However, the runway rollout alignment was significantly misaligned by 31.3 meters from the centerline.
The aircraft then taxied to the parking area from the runway, a process that took 6 minutes and covered a distance of less than 1 nautical mile. The total flight distance was 541 nautical miles, and the flight duration was 110 minutes. The aircraft used 4,547 kilograms of fuel during the flight.
The Airbus A321 aircraft successfully landed on runway 28R at San Francisco International Airport (KSFO) with a score of 76.1%. The final approach was initiated from the southeast, heading 298.0° at a distance of 4 nautical miles and an altitude of 1,262 feet above ground level (agl). The aircraft successfully touched down on the runway, with a touchdown speed of 122 kt, which was within the acceptable range.
However, there were some areas of concern during the landing. The threshold height at 70 ft agl was above the target, indicating that the aircraft may have been slightly high on its approach. Additionally, the runway touchdown position was misaligned by 11.4 meters from the centerline, which could have contributed to the subsequent rollout alignment issues.
The local weather conditions at the time of the landing were characterized by a temperature of 13°C and a wind speed of 25 kt from 180°. This resulted in a crosswind of 22 kt and a tailwind of 12 kt, which may have affected the aircraft's stability and control during the landing. Despite these conditions, the pilot managed to maintain a firm touchdown rate of -300 fpm.
The total landing distance was 1,953 meters, which accounted for 56% of the runway length. This is a relatively short landing distance, indicating that the pilot was able to bring the aircraft to a stop quickly and efficiently. However, the runway rollout alignment was significantly misaligned by 31.3 meters from the centerline, which could have been a result of the initial touchdown position being off-center.
Overall, while the landing was successful, there were some areas of concern that need to be addressed to improve the pilot's performance. With some adjustments to the approach and touchdown technique, the pilot may be able to achieve a higher score and improve the overall safety and efficiency of the landing.
Scroll or drag the slider to zoom · double-click to reset · hover for values