Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
Events
MY FS FLIGHTS
Flight Score
Departure
Use coordinated aileron input to level the wings and hold bank angle close to wings-level during the climb.
What happened: During the initial climb, your average bank angle drifted to 1.9°.
Watch for: Attitude indicator, bank angle near wings-level
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 203 fpm of sink returning after the arrest; a balloon like this usually carries through to a firm touchdown, as it did here at 717 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 · 25 stages, 23 scored
Events
Events
Events
Events
Events
Events
Events
Events
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.
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: speed above the reference speed.
The approach, gate by gate
Side view — the last 1,524 m of the approach.
Plan view — the first 1,524 m of the 3,397 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 Perth International Airport. This process took a mere one minute and covered less than a nautical mile. Once clear of the departure path, the aircraft executed a takeoff roll on runway 21. Reaching a speed of 162 knots, the A320 lifted off the ground in a mere 37% of the 1,291-meter runway.
As the aircraft soared into the sky, it was buffeted by gentle winds blowing at 18 knots from a direction of 239 degrees. This led to a crosswind component of 13 knots and a headwind component also worth 13 knots. Departing the Perth region, the A320 ascended to a height of 3,611 meters (11,907 feet) above sea level, marking the onset of its enroute climb. Over the town of Cloverdale, the aircraft commenced this ascent phase, rising by an impressive 3,371 meters in just 15 minutes while covering a distance of 94 nautical miles.
Once airborne, the crew initiated a level cruise, a phase that lasted for an extended period of 366 minutes. This cruise path took the aircraft to a distance of 2,754 nautical miles south-west of Cervantes, a significant stretch across the Indian Ocean. The aircraft's ascent from the Perth region and descent phases were punctuated by brief level cruises and climbs at various stages over the flight path.
One such climb took place 92 miles south-east of Weerawila Airport in Sri Lanka. Here, the crew guided the A320 upward by 807 feet in just two minutes while covering a distance of 11 nautical miles. This climb preceded the start of a further level cruise that lasted for 73 minutes, covering 427 nautical miles as the aircraft continued on its south-easterly course towards India.
The final descent phase began near the city of Munnar, a region of Kerala known for its lush tea plantations and diverse wildlife. As the aircraft plummeted towards the ground, it encountered varying weather conditions throughout its descent route. Eventually, the A320 made its final approach to runway 27 at Cochin International Airport, an airfield located near the bustling port city of Kochi.
Upon touchdown on the 3,397-meter runway, the A320 experienced some issues. The threshold height was significantly higher than expected, while the aircraft's touchdown speed was also too high at 153 knots. Furthermore, its touchdown point lay 216 meters beyond the designated touchdown zone.
The post-landing phase revealed that the A320 had covered a total distance of 3,449 nautical miles, having used a significant 15,078 kilograms of fuel over the flight's 587-minute duration. The aircraft's final taxiing phase from the runway to the parking area took merely three minutes, a testament to its exceptional maneuverability and efficient operational procedures.
The aircraft, an Airbus A320, attempted a landing on runway 27 at Cochin International Airport (VOCI). At 3 nautical miles from the airport, heading east, the aircraft was at an altitude of 563 feet above ground level (agl) and a distance of 271.0° from the runway.
The key performance parameters for this landing were evaluated as follows: the final approach path significantly exceeded the target threshold height, reaching 83 ft agl, which was higher than expected. Additionally, the aircraft's touchdown speed of 153 knots was higher than the target touchdown speed, which could have contributed to potential difficulties during the landing process.
At the point of touchdown, the aircraft was located 216 meters beyond the designated touchdown zone, and the touchdown speed was 144 knots, which was still relatively high. Furthermore, the aircraft's descent rate was quite rapid, reaching a rate of -689 feet per minute, which is indicative of a heavier-than-ideal touchdown.
Another critical issue with this landing was the runway alignment: when the aircraft touched down, it was 24.7 meters off-centerline, indicating that the pilot had difficulty aligning the aircraft with the runway. This misalignment may have contributed to difficulties during the braking or post-touchdown maneuvers.
Taking into account the weather conditions, which included a temperature of 30°C and a light crosswind of 5 kt with a moderate headwind of 6 kt, it's surprising that the pilot was unable to achieve a more precise alignment with the runway. The significant runway length of 3,397 meters was likely sufficient to accommodate a longer landing roll, but the pilot's decision to land with an excessive speed and a high descent rate undoubtedly added to the overall difficulties experienced during the landing process.
Ultimately, the total landing distance covered 1,166 meters, accounting for only 34% of the runway length. Unfortunately, the post-touchdown alignment with the runway was again excessively misaligned by 171.5 meters from the centerline.
Scroll or drag the slider to zoom · double-click to reset · hover for values