If you wish to contribute or participate in the discussions about articles you are invited to join SKYbrary as a registered user
A320, Khartoum Sudan, 2005
From SKYbrary Wiki
Revision as of 15:25, 4 April 2019 by Integrator3
|On 11 March 2005, an Airbus A321-200 operated by British Mediterranean Airways, executed two unstable approaches below applicable minima in a dust storm to land in Khartoum Airport, Sudan. The crew were attempting a third approach when they received information from ATC that visibility was below the minimum required for the approach and they decided to divert to Port Sudan where the A320 landed without further incident.|
|Actual or Potential
|Controlled Flight Into Terrain (CFIT), Human Factors, Weather|
|Flight Conditions||On Ground - Low Visibility|
|Operator||British Mediterranean Airways|
|Type of Flight||Public Transport (Passenger)|
|Origin||Amman/Queen Alia International|
|Intended Destination||Khartoum International Airport|
|Actual Destination||Port Sudan International Airport|
|Take off Commenced||Yes|
|Flight Phase||Missed Approach|
|Location - Airport|
|Airport||Khartoum International Airport|
|Tag(s)||Approach not stabilised,|
Non Precision Approach
|Tag(s)||IFR flight plan,|
Lateral Navigation Error,
No Visual Reference,
Vertical navigation error
|Tag(s)||Data use error,|
Procedural non compliance
|Tag(s)||Sand/Dust limited Forward Visibility|
|Safety Net Mitigations|
|Damage or injury||No|
|Causal Factor Group(s)|
On 11 March 2005, an Airbus A321-200 operated by British Mediterranean Airways, executed two unstable approaches below applicable minima in a dust storm to land in Khartoum Airport, Sudan. The crew were attempting a third approach when they received information from ATC that visibility was below the minimum required for the approach and they decided to divert to Port Sudan where the A320 landed without further incident.
"[…] Runway 36 was in use but the ILS on this runway was out of service. The commander assessed the weather conditions passed to him by ATC and believed that he was permitted, under his company’s operations policy, to carry out a Managed Non-Precision Approach (MNPA) to Runway 36. This type of approach requires the autopilot to follow an approach path defined by parameters stored in the aircraft’s commercially supplied Flight Management and Guidance System (FMGC) navigation database.
On the pilot’s approach chart, which was also commercially supplied but from a different supplier, the final descent point was depicted at 5 nm from the threshold of Runway 36 whereas the FMGC’s navigational database had been correctly updated with a recent change to this position published by the Sudanese CAA which placed it at 4.4 nm from the threshold. The discrepancy amounted to a difference in descent point of 0.6 nm from the Khartoum VOR/DME beacon, the primary navigation aid for the non-precision approach.
The pilots commenced the approach with the autopilot engaged in managed modes (ie the approach profile being determined by the FMGC instead of pilot selections). The aircraft began its final descent 0.6 nm later than the pilots were expecting. Believing the aircraft was high on the approach, the handling pilot changed the autopilot mode in order to select an increased rate of descent. The approach became unstable and the aircraft descended through 1,000 ft agl at an abnormally high rate. The aircraft then passed through its Minimum Descent Altitude (equivalent to a height of 390 ft agl) with neither pilot having established the required visual references for landing. Instead each pilot believed, mistakenly, that the other pilot was in visual contact with the runway approach lights.
When the confusion between the two pilots became apparent, the aircraft had descended to approximately 180 ft agl and the handling pilot commenced a go-around. Between 3.4 and 5.1 seconds later, with the aircraft at a radio altitude of approximately 125 ft agl, in a position approximately 1.5 nm short of the runway, the Terrain Avoidance and Warning System “TERRAIN AHEAD, PULL UP ” audio warning was triggered. The correct emergency pull-up procedure was not followed in full, partly because the handling pilot had already initiated a go-around. The minimum recorded terrain clearance achieved during the recovery manoeuvre was 121 ft.
One further non-precision approach to Runway 36 was attempted using selected autopilot modes…"
Causal Factors and Recommendations
The following causal factors are identified in the Report:
- "The pilots were unaware of a significant discrepancy between the approach parameters on the approach chart and those within the navigation database because they had not compared the two data sets before commencing the approach.
- Confusion regarding the correct approach profile and inappropriate autopilot selections led to an unstable approach.
- The unstable approach was continued below Minimum Descent Altitude without the landing pilot having the required visual references in sight.
- The UK CAA’s guidance and the regulatory requirements for approval to conduct MNPA were fragmented and ill-defined.
- The operator’s planning and implementation of MNPA (Managed Non‑Precision Approaches) procedures included incomplete operational and written procedures and inconsistent training standards.
- The ability of the installed EGPWS to provide sufficient warning of inappropriate terrain closure during the late stages of the approach was constrained by the lack of a direct data feed from the GPS navigation equipment."
The following Safety Recommendations are made in the Report:
- "Airbus should revise the expanded information ‘Pull up to full backstick and maintain’ of the A320 Emergency Procedure for the EGPWS Alert “TERRAIN TERRAIN PULL UP ” to remove any ambiguity about the amount of rearwards sidestick that should be applied.
- Airbus should expedite publication of guidance material relevant to flight and ground operations by Airbus aircraft types in conditions of blowing sand or low drifting sand.
- The European Aviation Safety Agency, in conjunction with industry, should review the current GPWS/TAWS system design criteria (ETSO-C151a), and installation certification criteria, with particular emphasis on the timeliness of alerting when close to the runway. Revisions to these standards arising from this review should apply retrospectively to all aircraft currently covered by the TAWS mandate.
- The UK CAA should publish guidance to pilots regarding the appropriate action when faced with a conflict in approach parameters between their approach charts and an FMS database authorised for managed non-precision approaches.
- Sand Storm
- Stabilised Approach
- Flying a Manual Go-around
- Response to a "PULL UP" Warning
- CFIT After Aborted VOR-DME Approach (OGHFA SE)
- The full UK AAIB report on the Serious Incident.