Crash of a Hawker 800XP near Bath: 3 killed

Date & Time: Oct 16, 2025 at 1727 LT
Type of aircraft:
Registration:
XA-JMR
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Battle Creek - Battle Creek
MSN:
258530
YOM:
2001
Location:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Circumstances:
The airplane departed Battle Creek-Kellogg Field-Executive Airport Runway 23R at 1708LT on a post maintenance test flight, carrying three crew members. After takeoff, the airplane bounded to the northeast then reached the assigned altitude of 15,000 feet before proceeding over Lansing. Apparently while performing stall maneuvers, the crew lost control of the airplane that entered a spin and crashed about a minute later in a field located near Bath. The airplane exploded on ground and was totally destroyed. All three occupants were killed. It was reported that the airplane arrived at Battle Creek Airport on 25 March 2025 and the present flight was the first since this date.

Crash of a Hawker 800XP in Fès

Date & Time: Apr 11, 2025 at 1511 LT
Type of aircraft:
Operator:
Registration:
CN-TKC
Flight Type:
Survivors:
Yes
Schedule:
Marrakech – Fès
MSN:
258670
YOM:
2004
Flight number:
AOM500C
Country:
Region:
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
After landing on runway 09 at Fès-Saïss Airport, the airplane was unable to stop within the remaining distance. It overran, collided with a concrete wall located 168 metres past the runway end, lost its undercarriage and both wings then made a 180 turn and came to rest. All three crew members were injured and the airplane was destroyed.

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 Hawker 800XP in Farmingdale

Date & Time: Dec 20, 2020 at 2035 LT
Type of aircraft:
Operator:
Registration:
N412JA
Flight Type:
Survivors:
Yes
Schedule:
Miami - Farmingdale
MSN:
258516
YOM:
2001
Flight number:
TFF941
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
4188
Captain / Total hours on type:
2060.00
Copilot / Total flying hours:
10000
Copilot / Total hours on type:
4100
Aircraft flight hours:
12731
Circumstances:
The flight crew were conducting an instrument landing system (ILS) approach in night instrument meteorological conditions when they were advised by the tower controller that the weather had deteriorated below minimums. The captain was the pilot monitoring, and the first officer was the pilot flying during the approach. Since the airplane was inside the final approach fix and stabilized, both pilots agreed to continue with the approach. Both pilots stated that they had visual contact with the runway approach lighting system at the 200 ft above ground level (agl) decision altitude, and they decided to continue the approach. The first officer said he then returned to flying the airplane via instruments. As the first officer continued the approach, the captain told him the airplane was drifting right of the runway centerline. The first officer said that he looked outside, saw that the weather had deteriorated, and was no longer comfortable with the approach. The first officer said he pressed the takeoff and go-around switch, while at the same time, the captain called for a go-around. The captain said that he called for the go-around because the airplane was not aligned with the runway. Although both pilots stated that the go-around was initiated when the airplane was about 50 to 100 ft agl, the cockpit voice recorder (CVR) recording revealed that the first officer flew an autopilot-coupled approach to 50 ft agl (per the approach procedure, a coupled approach was not authorized below 240 ft agl). As the airplane descended from 30 to 20 ft agl, the captain told the first officer three times to “flare” then informed him that the airplane was drifting to right and he needed to make a left correction to get realigned with the runway centerline. Three seconds passed before the first officer reacted by trying to initiate transfer control of the airplane to the captain. The captain did not take control of the airplane and called for a go-around. The first officer then added full power and called for the flaps to be retracted to 15º; however, the airplane impacted the ground about 5 seconds later, resulting in substantial damage to the fuselage. Data downloaded from both engines’ digital electronic engine control units revealed no anomalies. No mechanical issues with the airplane or engines were reported by either crew member or the operator. The sequence of events identified in the CVR recording revealed that the approach most likely became unstabilized after the autopilot was disconnected and when the first officer lost visual contact with the runway environment. The captain, who had the runway in sight, delayed calling for a go-around after the approach became unstabilized, and the airplane was too low to recover.
Probable cause:
The flight crew’s delayed decision to initiate a go-around after the approach had become unstabilized, which resulted in a hard landing.
Final Report: