Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
MY FS FLIGHTS
Flight Score
Departure
Make small rudder corrections against a point at the far end to hold the centreline.
What happened: During the ground roll you drifted 4.9 m off the runway centreline.
Watch for: Watch runway alignment against the centreline, correcting with small rudder inputs.
See Departure Roll
Arrival
Fly the flare as one continuous check of the sink rate from 17 ft, holding back pressure steadily rather than adjusting pitch piecemeal.
What happened: The flare drifted away from its intended profile rather than tracking it smoothly from 17 ft down to touchdown.
Watch for: Watch radio altitude and VSI through the flare, aiming to arrest the sink smoothly from 17 ft to touchdown.
See Arrival Landing
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
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.
At the 1,000 ft gate: sink rate above what the glideslope needed.
The approach, gate by gate
Side view — the last 2,862 m of the approach.
Plan view — the first 2,862 m of the 4,121 m runway, to the same scale as the side view.
Touched down 1,238 m past the threshold — beyond the full-score zone. The arrival was smooth.
The rest of the report
A Boeing 777F took off from runway 03L at OR Tambo International Airport, Johannesburg. The departure roll was smooth, covering the first 73% of the runway in 2,927 meters. The aircraft lifted off at a speed of 166 knots, heading into the local weather conditions of a temperature of 30°C, with a wind speed of 4 knots at 290 degrees, producing a negligible headwind.
As the aircraft entered the enroute climb phase, it began ascending from an elevation of 6,419 feet above sea level. The climb was steep, reaching an altitude of 34,976 feet in just 15 minutes, covering a distance of 102 nautical miles. This marked the start of the enroute level cruise phase, where the aircraft remained at a steady altitude for 162 minutes, covering an impressive 1,361 nautical miles.
In the subsequent enroute descent phase, the aircraft began its descent from an altitude of 35,305 feet, reaching a landing elevation of 6,873 feet in 19 minutes, covering a distance of 104 nautical miles. The final approach to runway 06 at Jomo Kenyatta International Airport was made from the southwest, at a heading of 58.0 degrees and an altitude of 4 nautical miles and 1,554 feet above ground level.
The landing on runway 06 was notable for its slight misalignment from the touchdown zone, with the aircraft touching down 812 meters beyond the designated area. The touchdown speed of 144 knots was considered good, and the touchdown rate of -162 feet per minute was also within acceptable limits. However, the runway touchdown position was misaligned by 12.7 meters from the centreline.
The post-landing rollout was slightly misaligned from the centreline, by 15.2 meters. The total landing distance of 2,771 meters was 67% of the runway. After a taxiing period of 5 minutes, the aircraft arrived at the parking area, having covered a distance of 2 nautical miles and consumed 26,472 kilograms of fuel throughout the flight.
Overall, the Boeing 777F flight was a successful operation, covering a total distance of 1,579 nautical miles in 211 minutes.
The Boeing 777F aircraft completed a final approach to runway 06 at Jomo Kenyatta International Airport, landing safely. However, the approach was not without some notable deviations from the ideal performance. The aircraft was approaching from the southwest, heading 58.0 degrees, at 4 nautical miles and 1,554 feet above ground level.
Despite being above the target, the aircraft maintained a relatively smooth touchdown, touching down at a speed of 144 knots. Unfortunately, the touchdown speed was slightly higher than the optimal speed, and the touchdown point was located 812 meters beyond the designated touchdown zone. This indicates that the aircraft's touchdown was farther down the runway than desired. The landing rate, however, remained good at -162 feet per minute, indicating a controlled descent.
The runway touchdown position was also misaligned by approximately 12.7 meters from the centerline, suggesting that the aircraft was not perfectly aligned with the runway during the final stages of the approach.
Given the local weather conditions, with a temperature of 17 degrees Celsius and wind speeds of 3 knots from 160 degrees, the aircraft was subjected to a gentle crosswind. Nonetheless, the crew successfully coped with this condition and maintained control of the aircraft throughout the landing.
The total landing distance covered 2,771 meters, representing approximately 67% of the runway length. While not excessively long, this landing distance suggests that the aircraft required a bit more runway to come to a stop, likely due to the slightly higher-than-optimal touchdown speed. The runway rollout alignment was also slightly misaligned by 15.2 meters from the centerline, although this deviation was not as significant as the touchdown point position.
Overall, while the aircraft landed safely, the crew's performance could be considered average, with a final score of 79.2%. This score reflects a combination of factors, including the slightly above-target touchdown speed, significant deviations from the touchdown zone and centerline, and the moderate landing distance.
Scroll or drag the slider to zoom · double-click to reset · hover for values