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 5.7 m off the runway centreline.
Watch for: Watch runway alignment against the centreline, correcting with small rudder inputs.
See Departure Roll
Arrival
Carry more power on short final to hold 141 kt at the threshold instead of letting speed decay before the flare.
What happened: The threshold was crossed at 139 kt against a VREF of 141 kt, already below target, and the sink was fully arrested at 20 ft with speed continuing to bleed off - crossing the threshold slow like this usually carries forward into the aircraft settling on as the speed runs out, rather than flying onto the mains.
Watch for: Airspeed indicator against 141 kt on short final.
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 · 15 stages, 13 scored
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 152 m above the runway. The 305 m gate was not assessed, because the approach did not join final that far out.
At the 152 m 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 1,524 m of the approach.
Plan view — the first 1,524 m of the 2,387 m runway, to the same scale as the side view.
Touched down 670 m past the threshold — beyond the full-score zone. The arrival was smooth.
The rest of the report
The flight began with the Airbus A320 taxiing from the parking area to the runway at Amsterdam Airport Schiphol, taking 13 minutes and covering a distance of 2 nautical miles. The departure roll took place on runway 36L, with a takeoff distance of 1,661 meters, which is 47% of the runway length. The aircraft lifted off at a speed of 166 knots.
As the flight progressed, the aircraft began its enroute climb, starting 1 mile north east of Vijfhuizen, a location in the Netherlands. The climb took 19 minutes, during which the aircraft ascended from an altitude of 317 meters above sea level to 11,279 meters above sea level, an increase of 10,962.6 meters. The enroute climb covered a distance of 114 nautical miles.
Following the climb, the aircraft entered a level cruise phase, which started 1 mile south east of Solingen, a location in Germany. This phase lasted for 63 minutes and covered a distance of 463 nautical miles. The cruise phase was a stable and efficient part of the flight.
As the aircraft approached its destination, it began its enroute descent, starting 3 miles north of Mrkopalj, a location in Croatia. The descent took 27 minutes, during which the aircraft descended from an altitude of 11,280 meters above sea level to 169 meters above sea level, a decrease of 11,111.5 meters. The enroute descent covered a distance of 126 nautical miles.
The final approach to runway 23 at Split Airport took place from the north east, with the aircraft heading 233.0 degrees at an altitude of 142.3 meters above ground level and 1 nautical mile from the runway. The landing took place on runway 23, which has a length of 2,387 meters. The threshold height was above the target, but the threshold speed was good at 139 knots.
The touchdown point was 250 meters beyond the touchdown zone, with a touchdown speed of 128 knots, which was good. The touchdown rate was perfect at 0.1 meters per second. However, the runway touchdown position was slightly misaligned by 6.2 meters from the centerline. The total landing distance was 1,430 meters, which is 60% of the runway length. The runway rollout alignment was very good.
The flight concluded with the aircraft taxiing to the parking area from the runway, taking 3 minutes and covering a distance of less than 1 nautical mile. The total flight distance was 709 nautical miles, and the flight duration was 126 minutes. The aircraft used 4,258 kilograms of fuel during the flight.
The Airbus A320 successfully landed at LDSP Split Airport, achieving an overall score of 85.2%. The aircraft was approaching the runway from the north-east, heading 233.0° at 1 nautical mile and 142.3 meters above ground level (agl). The final approach was executed with precision, and the aircraft landed on runway 23, which has a length of 2,387 meters.
Upon touchdown, the aircraft's speed was 128 knots, which is within the acceptable range. The touchdown rate was also perfect at 0.1 meters per second, indicating a smooth and controlled landing. However, the touchdown point was 250 meters beyond the designated touchdown zone, which may require further analysis to determine the cause of this deviation.
The threshold height at 19.4 meters agl was above the target, suggesting that the aircraft may have been slightly higher than desired during the final approach. Nevertheless, the threshold speed was good at 139 knots, indicating that the pilot maintained control and adhered to the recommended speed.
The runway touchdown position was slightly misaligned by 6.2 meters from the centerline, which may require adjustments to the pilot's approach and landing technique. Local weather conditions were favorable, with a temperature of 27°C, which did not appear to affect the landing.
The total landing distance was 1,430 meters, accounting for 60% of the runway length. This is a relatively short landing distance, indicating that the pilot executed the landing with precision and control. The runway rollout alignment was also very good, suggesting that the pilot maintained control and stability during the rollout phase.
Overall, the landing was successful, but there are areas for improvement, particularly in terms of touchdown point accuracy and runway alignment. Further analysis and training may be necessary to refine the pilot's skills and achieve a higher score.
Scroll or drag the slider to zoom · double-click to reset · hover for values