What happened
On 13 April 2007, an Airbus A300 B4, registration TC-MND, was conducting a commercial cargo flight into Manchester Airport. The crew was cleared to perform a VOR/DME approach for Runway 24L. During the approach, the aircraft's descent profile deviated from the published requirements.
As the aircraft progressed along the approach, radar monitoring by the Tower controller revealed that the aircraft was positioned approximately 1 nm to the right of the published track. At a distance of 5 nm from the touchdown threshold, the controller observed the aircraft appearing low and subsequently instructed the crew to perform a go-around. The crew ceased their descent and, after confirming the runway was in sight, completed the landing without further incident.
The investigation
The investigation examined radar recordings, air traffic control frequencies, and the published approach procedures for Manchester Airport. Due to a delay in reporting the incident, the AAIB was unable to retrieve data from the aircraft's flight data recorder or cockpit voice recorder.
Radar analysis indicated that the aircraft was north of the published approach track for Runway 24L, though it remained within prescribed lateral tolerances. However, the vertical data showed that the aircraft had descended below the minimum altitude of 2,400 ft before passing the Final Approach Fix (FAF). Specifically, at the Step Down Fix (SDF) located 5 nm from the MCT VOR, the aircraft was below the required altitude of 2,080 ft.
Findings
- The aircraft descended below the minimum altitude required by the published procedure.
- The flight profile suggests the crew was utilizing a stepped descent technique rather than a stabilized approach.
- While the aircraft was slightly off the published track, it was within the allowable limits for the approach segment.
- The crew did not misidentify the approach; the track followed did not correspond to the Runway 24R procedure.