Region

Crash of a Boeing 737-4Y0 in Abuja

Date & Time: Dec 11, 2024 at 1006 LT
Type of aircraft:
Operator:
Registration:
5N-JRT
Flight Type:
Survivors:
Yes
Schedule:
Lagos - Abuja
MSN:
26081/2442
YOM:
1993
Flight number:
AJK206
Country:
Region:
Crew on board:
5
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The airplane was on a cargo service (flight AJK206) from Lagos with a crew of five on board. After landing on runway 22 at Abuja-Nnamdi Azikiwe Airport, the airplane veered off runway to the right. Contacting soft ground, it lost a gear and came to a halt in a ditch. All five crew members escaped uninjured.

Crash of a Hawker 800XP in Ibadan

Date & Time: Nov 3, 2023 at 2018 LT
Type of aircraft:
Operator:
Registration:
5N-AMM
Survivors:
Yes
Schedule:
Abuja - Ibadan
MSN:
258286
YOM:
1995
Flight number:
IB500
Location:
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3864
Captain / Total hours on type:
335.00
Copilot / Total flying hours:
2030
Copilot / Total hours on type:
1730
Aircraft flight hours:
10492
Aircraft flight cycles:
7195
Circumstances:
The airplane departed Abuja-Nnamdi Azikiwe Airport at 1941LT on a charter flight (IB500) to Ibadan, carrying seven passengers and three crew members. At 2013LT, the crew was cleared to land on runway 22 and continued the approach. On short final, the airplane impacted the first row of approach lights on the approach path, then touched down first with the right main landing gear, about 220 metres short of the threshold of the runway, and in the grass verge, followed shortly by the left main and nose landing gears respectively. The aircraft continued towards the paved area of the runway, impacting several other rows of approach lights along its path. A total of six impact points were observed. Subsequently, the aircraft entered the paved area and veered right of the centerline, runway 22. At about 156 metres from the threshold, the aircraft crossed the right runway shoulder and continued into the grass verge for a distance of about 184 metres before coming to a stop, partially impeded by vegetation. Number one tyre was found deflated and the nose landing gear collapsed. All 10 occupants disembarked safely.
The below preliminary report was quickly published by NSIB.
Final Report:

Crash of a Beechcraft 350 Super King Air in Kaduna: 11 killed

Date & Time: May 21, 2021 at 1800 LT
Operator:
Registration:
NAF203
Flight Type:
Survivors:
No
MSN:
FL-891
YOM:
2013
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
7
Pax fatalities:
Other fatalities:
Total fatalities:
11
Circumstances:
On final approach to Kaduna Airport in poor weather conditions, the twin engine aircraft crashed, bursting into flames. The aircraft was totally destroyed by impact forces and a post crash fire. All 11 occupants were killed, among them General Ibrahim Attahiru, Chief of Staff of the Nigerian Army. He was returning to Kaduna with a delegation of six other Army officers, among them three Brigadier General.
Crew:
F/Lt T. Asaniyi,
F/Lt A. Olufade,
Sgt Adesina,
Acm Oyedepo.
Passengers:
Lt General Ibrahim Attahiru,
Br/Gen M. Abdulkadir,
Br/Gen Olayinka,
Br/Gen Kuliya,
Maj Lawal Hayat,
Maj Hamza,
Sgt Umar.

Crash of a Beechcraft 350 Super King Air in Abuja: 7 killed

Date & Time: Feb 21, 2021 at 1148 LT
Operator:
Registration:
NAF201
Flight Type:
Survivors:
No
Schedule:
Abuja - Minna
MSN:
FL-585
YOM:
2008
Country:
Region:
Crew on board:
2
Crew fatalities:
Pax on board:
5
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
After takeoff from Abuja-Nnamdi Azikiwe Airport, while climbing, the crew informed ATC about an engine failure and was cleared for an immediate return. On final approach to runway 22, the aircraft went out of control and crashed in an open field, bursting into flames. The aircraft was destroyed and all 7 occupants were killed, among them two pilots, four ATOS specialists (Airborne Tactical Observation System) and one technician.

Crash of a Boeing 737-36N in Lagos

Date & Time: Jul 23, 2019 at 1128 LT
Type of aircraft:
Operator:
Registration:
5N-BQO
Survivors:
Yes
Schedule:
Port Harcourt - Lagos
MSN:
28571/3022
YOM:
1998
Flight number:
P47191
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
133
Pax fatalities:
Other fatalities:
Total fatalities:
0
Aircraft flight hours:
45452
Aircraft flight cycles:
31643
Circumstances:
Following an uneventful flight from Port Harcourt, the crew initiated the approach to Lagos-Murtala Muhammed Airport in poor weather conditions with heavy rain falls due to CB's at 1,900 feet. On final, he was cleared to land on runway 18R and informed about a wet runway surface. Both main landing gears touched down normally and when the nose gear landed as well, both wheels apparently separated. The nose gear leg ripped the ground and the airplane rolled for few dozen metres before coming to rest. All 139 occupants evacuated safely and the airplane was later considered as damaged beyond repair.

Crash of a Gulfstream G200 in Abuja

Date & Time: Jan 25, 2018 at 1520 LT
Type of aircraft:
Operator:
Registration:
5N-BTF
Survivors:
Yes
Schedule:
Lagos - Abuja
MSN:
180
YOM:
2007
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
4
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5300
Captain / Total hours on type:
280.00
Copilot / Total flying hours:
5700
Copilot / Total hours on type:
93
Aircraft flight hours:
1421
Aircraft flight cycles:
921
Circumstances:
On 25th January 2018 at 14:28 h, a Gulfstream 200 (G200) aircraft with nationality and registration marks 5N-BTF operated by Nestoil Plc, departed Murtala Mohammed International Airport, Lagos (DNMM) as a charter flight to Nnamdi Azikiwe International Airport, Abuja (DNAA) on an Instrument Flight Rules (IFR) flight plan. Onboard were four passengers and three flight crew members. The Pilot in command (PIC) was the Pilot Monitoring (PM) and the Co-pilot was the Pilot Flying (PF). The departure, cruise and approach to Nnamdi Azikiwe International Airport were normal. At 14:45 h, 5N-BTF contacted Abuja radar and was subsequently cleared for Radar vectors ILS approach Runway 22. Abuja Airport Automatic Terminal Information Service (ATIS) Papa for time 14:20 h was monitored as follows; “Main landing runway 22, wind 110/07 kt, Visibility 3,500 m in Haze, No Significant Clouds, Temperature/Dew point 33/- 01°C, QNH 1010 hPa, Trend No Significant Change, End of Information Papa”. At 15:17 h, 5N-BTF reported 4 NM on Instrument approach (ILS) and was requested to report 2 NM because there was a preceding aircraft (Gulfstream 5) on landing roll. Thereafter, 5N-BTF was cleared to land runway 22 with reported wind of 070°/07 kt. At 15:18 h, the aircraft touched down slightly left of the runway centre line. According to the PF, in the process of controlling the aircraft to the centre line, the aircraft skidded left and right and eventually went partly off the runway to the right where it came to a stop. In his report, the PM stated that on touchdown, he noticed the aircraft oscillating left and right as brakes were applied. The oscillation continued to increase and [the aircraft] eventually went off the runway to the right where the aircraft came to a stop, partially on the runway. During the post-crash inspection, the investigation determined that the skid marks on the runway indicated that the aircraft steered in an S-pattern continuously with increasing amplitude, down the runway. On the last right turn, the aircraft exited the right shoulderof the runway, the right main wheel went into the grass and on the final left turn, the right main landing gear strut detached from its main attachment point after which the aircraft finally came to a complete stop on a magnetic heading of 160°. The ATC immediately notified the Aircraft Rescue and Fire Fighting Services (ARFFS), Approach Radar Control, and other relevant agencies about the occurrence. All persons on board disembarked with no injuries. Instrument Meteorological Conditions (IMC) prevailed at the time of the occurrence. The serious incident occcurred in daylight.
Probable cause:
Causal Factor:
The use of improper directional control techniques to maintain the aircraft on the runway.
Contributory Factor:
Improper coordination in taking over control of the aircraft by the PM which was inconsistent with Nestoil SOP.
Final Report:

Crash of a Dornier DO228-212 in Kaduna: 7 killed

Date & Time: Aug 29, 2015 at 0647 LT
Type of aircraft:
Operator:
Registration:
NAF030
Flight Phase:
Flight Type:
Survivors:
No
Site:
Schedule:
Kaduna – Abuja
MSN:
8219
YOM:
1993
Country:
Region:
Crew on board:
4
Crew fatalities:
Pax on board:
3
Pax fatalities:
Other fatalities:
Total fatalities:
7
Circumstances:
Shortly after takeoff from the Kaduna Military Airfield, while climbing, the aircraft went out of control and crashed into a house located in the Ribadu Cantonment, bursting into flames. All seven occupants (two pilots, two engineers and three passengers) were killed.

Crash of a Hawker 800XP in Port Harcourt

Date & Time: Jun 8, 2015 at 1916 LT
Type of aircraft:
Registration:
N497AG
Survivors:
Yes
Schedule:
Abuja – Port Harcourt
MSN:
258439
YOM:
1999
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4180
Captain / Total hours on type:
2752.00
Copilot / Total flying hours:
16744
Copilot / Total hours on type:
147
Aircraft flight hours:
8447
Aircraft flight cycles:
6831
Circumstances:
On 11th June, 2015, at about 18:25 h, an HS-125-800XP aircraft with nationality and registration marks N497AG, operated by SWAT Technology Limited departed Nnamdi Azikiwe International Airport, Abuja (DNAA) for Port Harcourt International Airport (DNPO) as a charter flight on an Instrument Flight Rule (IFR) flight plan. There were five persons on board inclusive of three flight crew and two passengers. The Captain was the Pilot Flying while the Co-pilot was the Pilot Monitoring. At 18:48 h, N497AG established contact with Lagos and Port Harcourt Air Traffic Control (ATC) units cruising at Flight Level (FL) 280. At 18:55 h, the aircraft was released by Lagos to continue with Port Harcourt. Port Harcourt cleared N497AG for descent to FL210. At 19:13 h, the crew reported field in sight at 6 nautical miles to touch down to the Tower Controller (TC). TC then cleared the aircraft to land with caution “runway surface wet”. The crew experienced light rain at about 1.3 nautical miles to touch down with runway lights ON for the ILS approach. At about 1,000 ft after the extension of landing gears, the PM remarked ‘Okay...I got a little rain on the windshield’ and the PF responded, ‘We don’t have wipers sir... (Laugh) Na wa o (Na wa o – local parlance, - pidgin, for expression of surprise). From the CVR, at Decision Height, the PM called out ‘minimums’ while the PF called back ‘landing’ as his intention. The PM reported that the runway edge lights were visible on the left side. On the right side, it was missing to a large extent and only appeared for about a quarter of the way from the runway 03 end. The PM observed that the aircraft was slightly to the left of the “centreline” and pointed out “right, right, more right.” The PM further stated that at 50 ft, the PF retarded power and turned to the left. At 40 ft, the PM cautioned the PF to ‘keep light in sight don’t go to the left’. At 20 ft, the PM again said, ‘keep on the right’. PF replied, ‘Are you sure that’s not the centre line?’. At 19:16 h, the aircraft touched down with left main wheel in the grass and the right main wheel on the runway but was steered back onto the runway. The PF stated, “...but just on touchdown the right-hand lights were out, and in a bid to line up with the lights we veered off the runway to the left”. The nose wheel landing gear collapsed, and the aircraft stopped on the runway. The engines were shut down and all persons on board disembarked without any injury. From the CVR recordings, the PF told the PM that he mistook the brightly illuminated left runway edge lights for the runway centreline and apologized for the error of judgement for which the PM responded ‘I told you’. The aircraft was towed out of the runway and parked at GAT Apron at 21:50 h. The accident occurred at night in light rain.
Probable cause:
The accident was the consequence of a black hole effect disorientation causing low-level manoeuvre into grass verge.
The following contributing factors were identified:
- Most of the runway 21 right edge lights were unserviceable at landing time.
- Inadequate Crew Resource Management during approach.
Final Report:

Crash of a Boeing 747-281BSF in Abuja

Date & Time: Dec 4, 2013 at 2119 LT
Type of aircraft:
Operator:
Registration:
EK-74798
Flight Type:
Survivors:
Yes
Schedule:
Jeddah - Abuja
MSN:
23698/667
YOM:
1986
Flight number:
SV6814
Country:
Region:
Crew on board:
6
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
23000
Captain / Total hours on type:
13000.00
Copilot / Total flying hours:
5731
Copilot / Total hours on type:
1296
Aircraft flight hours:
94330
Aircraft flight cycles:
15255
Circumstances:
Following an uneventful cargo flight from Jeddah, the crew completed the approach and landing procedures on runway 04 at Abuja-Nnamdi Azikiwe Airport. During the landing roll, the aircraft overran the displaced threshold then veered to the right and veered off runway. While contacting a grassy area, the aircraft collided with several parked excavator equipment and trucks. The aircraft came to a halt and was severely damaged to both wings and engines. All six occupants escaped uninjured while the aircraft was damaged beyond repair.
Probable cause:
The accident resulted as the crew was not updated on the information available on the reduced runway length.
The following contributing factors were identified:
1. Lack of briefing by Saudia dispatcher during pre-flight.
2. Runway status was missing from Abuja ATIS information.
3. Ineffective communication between crew and ATC on short finals.
4. The runway markings and lighting not depicting the displaced threshold.
5. The entire runway lighting was ON beyond the displaced threshold.
Final Report:

Crash of an Embraer EMB-120ER Brasília in Lagos: 16 killed

Date & Time: Oct 3, 2013 at 0932 LT
Type of aircraft:
Operator:
Registration:
5N-BJY
Flight Phase:
Survivors:
Yes
Schedule:
Lagos - Akure
MSN:
120-174
YOM:
1990
Flight number:
SCD361
Country:
Region:
Crew on board:
7
Crew fatalities:
Pax on board:
13
Pax fatalities:
Other fatalities:
Total fatalities:
16
Captain / Total flying hours:
20068
Captain / Total hours on type:
1309.00
Copilot / Total flying hours:
4660
Copilot / Total hours on type:
3207
Aircraft flight hours:
27362
Aircraft flight cycles:
34609
Circumstances:
The crew discussed some concerns about the aircraft prior to departure but at this time we are not prepared to elaborate on those concerns as there remains a lot of work to complete on the CVR analysis in order to determine the specific nature of the crew’s concerns. Associated 361 was cleared for take-off on runway one eight left at Lagos international airport. The wind was calm and weather is not considered a factor in this accident. Approximately 4 seconds after engine power was advanced to commence the take-off roll, the crew received an automated warning from the onboard computer voice which consisted of three chimes followed by “Take-off Flaps…Take-off Flaps”. This is a configuration warning that suggests that the flaps were not in the correct position for take-off and there is some evidence that the crew may have chosen not to use flaps for the take-off. The warning did not appear to come as any surprise to the crew and they continued normally with the take-off. This warning continues throughout the take-off roll. As we are in the process of verifying the accuracy of the flight data, we have not yet been able to confirm the actual flap setting however we expect to determine this in the fullness of time. It was determined from the CVR that the pilot flying was the Captain and the pilot monitoring and assisting was the First Officer. The ‘set power‘ call was made by the Captain and the ‘power is set’ call was confirmed by the First Officer as expected in normal operations. Approximately 3 seconds after the ‘power is set’ call, the First Officer noted that the aircraft was moving slowly. Approximately 7 seconds after the ‘power is set’ call, the internal Aircraft Voice warning system could be heard stating ‘Take off Flaps, Auto Feather’. Auto feather refers to the pitch of the propeller blades. In the feather position, the propeller does not produce any thrust. The FDR contains several engine related parameters which the AIB is studying. At this time, we can state that the Right engine appears to be producing considerably less thrust than the Left engine. The left engine appeared to be working normally. The aircraft automated voice continued to repeat ‘Take-off Flaps, Auto Feather’. The physical examination of the wreckage revealed that the right engine propeller was in the feather position and the engine fire handle was pulled/activated. The standard ‘eighty knots’ call was made by the First Officer. The first evidence that the crew indicated that there was a problem with the take-off roll was immediately following the ‘eighty knots’ call. The First Officer asked if the take- off should be aborted approximately 12 seconds after the ‘eighty knots’ callout. Our investigation team estimates the airspeed to be approximately 95 knots. Airspeed was one of the parameters that, while working in the cockpit, appeared not to be working on the Flight Data Recorder. We were able to estimate the speed based on the radar data that we synchronized to the FDR and CVR but it is very approximate because of this. In response to the First Officer’s question to abort, the Captain indicated that they should continue and they continued the take-off roll. The crew did not make a ‘V1’ call or a Vr’ call. V1 is the speed at which a decision to abort or continue a take-off is made. Vr is the speed at which it is planned to rotate the aircraft. Normally the non-flying pilot calls both the V1 and the Vr speeds. When Vr is called the flying pilot pulls back on the control column and the aircraft is rotated (pitched up) to climb away from the runway. During the rotation, the First Officer stated ‘gently’, which we believe reflects concern that the aircraft is not performing normally and therefore needs to be rotated very gently so as not to aerodynamically stall the aircraft. The First Officer indicated that the aircraft was not climbing and advised the Captain who was flying not to stall the aircraft. Higher climb angles can cause an aerodynamic stall. If the aircraft is not producing enough overall thrust, it is difficult or impossible to climb without the risk of an aerodynamic stall. Immediately after lift-off, the aircraft slowly veered off the runway heading to the right and was not climbing properly. This aircraft behavior appears to have resulted in the Air Traffic Controller asking Flight 361 if operation was normal. Flight 361 never responded. Less than 10 seconds after rotation of the aircraft to climb away from the runway, the stall warning sounded in the cockpit and continued to the end of the recording. The flight data shows characteristics consistent with an aerodynamic stall. 31 seconds after the stall warning was heard, the aircraft impacted the ground in a nose down near 90° right bank.
Probable cause:
The accident was the consequence of the decision of the crew to continue the take-off despite the abnormal No. 2 Propeller rpm indication and a low altitude stall as a result of low thrust at start of roll for take-off from No. 2 Engine caused by an undetermined malfunction of the propeller control unit.
The following contributing factors were identified:
- The aircraft was rotated before attaining V1.
- The decision to continue the take-off with flap configuration warning and auto- feather warning at low speed.
- Poor professional conduct of the flight crew.
- Inadequate application of Crew Resource Management (CRM) principles.
- Poor company culture.
- Inadequate regulatory oversight.
Final Report: