Serious incident Boeing 737-5L9 5N-AIS,
ASN logo
ASN Wikibase Occurrence # 221612
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Thursday 3 January 2019
Type:Silhouette image of generic B735 model; specific model in this crash may look slightly different    
Boeing 737-5L9
Owner/operator:Azman Air
Registration: 5N-AIS
MSN: 29235/3076
Fatalities:Fatalities: 0 / Occupants: 114
Aircraft damage: None
Category:Serious incident
Location:near Port Harcourt -   Nigeria
Phase: Approach
Nature:Passenger - Scheduled
Departure airport:Lagos-Murtala Muhammed International Airport (LOS/DNMM)
Destination airport:Port Harcourt Airport (PHC/DNPO)
Investigating agency: AIB Nigeria
Confidence Rating: Information verified through data from accident investigation authorities
On January 3, 2019, at about 10:10 h, an Azman flight AZM 2316 departed Lagos for Port Harcourt in Nigeria. on an Instrument Flight Rule (IFR) Flight Plan with 109 passengers and five crew on board. The flight was the first flight of the day for the aircraft. There was no reported technical fault or observation on both engines during the previous flight.
The take-off and climb out phase was normal. The captain was the Pilot Flying (PF) and co-pilot was the Pilot Monitoring (PM). The aircraft levelled off at a cruising altitude of 29,000 ft (FL290). According to the Flight Data Recorder (FDR), Engines No. 1 and No. 2 were both showing 84.6% N1.
According to the flight crew, at some point during the cruise, about 20-25 minutes into the flight, they heard a loud bang which lasted for about 4-5 seconds followed by a yaw to the right. At about 10:28 FDR data revealed that the engine no. 2 N1 value started decreasing for about 4.3 seconds (which corresponds to the point at which the crew heard a bang and experienced a yaw).
The flight crew also stated that engine parameters look normal at that time and in addition, the purser reported that there was nothing unusual noticed in the cabin after the loud bang. The flight crew, therefore, assumed that the bang was associated with a cargo shift. The aircraft was on Autopilot (A/P) and Auto Throttle (A/T).
At about 10:42, Port Harcourt Approach cleared the aircraft for a straight in approach on runway 21; Flap 15° was selected, Localizer captured, Glideslope captured and the gears were selected DOWN. As the A/P disengaged, the aircraft suddenly yawed to the right accompanied by severe vibration and also thrust asymmetry was noticed. At that time, the aircraft was two dots below the glide slope and the field was not in sight. The PM noticed no.1 engine vibration indicating 3.0 to 3.5 units. No.1 engine N1 was 65%, no.2 engine N1 was 35% and the no.2 Oil Filter Bypass Light came ON. This led to precautionary shut down of no. 2 Engine by the crew.
FDR data also indicated that, at one point before the approach, the figure of engine instruments were indicating almost the same with no difference until about 10:53 h when the crew advanced the throttles individually in order to verify the engine outputs. At that time, the crew noticed that no. 2 engine did not respond appropriately to the throttle movement. FDR data also indicated that no. 2 engine was shut down five minutes after the verification of the engine output.
In order to figure out what was happening, the captain handed over control to the co-pilot. The crew accomplished the Severe Engine/Damage Checklist. However, the first approach became unstable and the crew executed a missed approach at about 10:55 h.
At about 11:09, when the ATC cleared the crew for the second approach, the response was that they were not ready for the approach at that moment. However, they requested for vectors as they were having a problem with no. 2 engine.
During the second approach to runway 21, the aircraft came high on the approach and was off track of the runway centreline. At about 11:19, the crew declared an emergency and executed a second missed approach. However, the crew were able to land the aircraft safely on runway 21 after the third approach at about 11:35.


Revision history:

06-Feb-2019 20:42 harro Added
06-Feb-2019 20:44 harro Updated [Damage]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314