FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24FA301 · Cessna 402B

11 Jul 2024 · Aguadilla, PR, United States

W J Medical Consulting Cessna 402B · Accident: loss of engine power (partial) on approach

From Rafael Hernández International Airport (BQN) to Luis Munoz Marin International Airport (SJU)

Report a problem

Event

NTSB case
ERA24FA301
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 402B

Aircraft type
Cessna 402
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N4167G
Onboard fatalities
Unknown
Route
From Rafael Hernández International Airport (BQN), Aguadilla, PRTo Luis Munoz Marin International Airport (SJU), San Juan, PR
Aircraft age
About 48 years (built 1976)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Approach · VFR pattern crosswind
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of engine power (partial)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft handling/service
  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

About 3 months before the accident, the twin-engine airplane underwent an annual maintenance inspection during which the mechanic identified numerous discrepancies with both engines and the airframe. The airplane was not subsequently approved for flight and the owner was provided a list of the discrepancies. The purpose of the accident flight was to relocate the airplane to another airport where the pilot planned to have the discrepancies addressed. The mechanic reported that he had advised the pilot that he needed to apply for a ferry permit from the FAA in order to complete the accident flight, but there was no evidence that the pilot had obtained one. On the day of the accident flight, air traffic control data showed that the pilot departed and climbed the airplane to about 1,500 ft mean sea level (msl). About 2 miles from the departure airport the pilot advised air traffic control of his intent to return to the departure runway due to a vibration of the right engine. The controller immediately cleared the pilot to enter the left downwind for the departure runway. The airplane then turned to the left and began a descent toward the left downwind leg of the traffic pattern. When the airplane was about a mile from the airport, the pilot reported that the airplane had an “engine failure” and that he intended to land on the departure runway, but in the opposite direction. Recorded flight track data showed that the airplane then turned directly toward the approach end of that runway and that during the final 30 seconds of track data, the airplane’s altitude and groundspeed decreased rapidly. Surveillance video captured the final few seconds of flight, and showed the airplane in a steep vertical descent and a right roll. The airplane impacted a residential area into trees, powerlines, and propane fuel tanks. After the impact, the airplane sustained significant postimpact fire damage. Postaccident examination of the airplane revealed no evidence of any preimpact mechanical malfunctions or failures of the airplane’s flight controls. Although the right engine’s fuel manifold was damaged by thermal forces, it contained visible corrosion and remains of diaphragm material when opened. Below the fuel screen at the fuel inlet within the manifold was a large quantity of debris and foreign material that was likely present before the accident. Based on the available evidence, it is possible that this contamination resulted in the total loss of engine power to the right engine that was reported by the pilot; however, given the multiple discrepancies that had been documented with the engine prior to the flight, and the extent of the post impact fire damage to the engine, it is possible that the loss of reported loss of engine power may have been due to other unresolved maintenance issues. The final recorded position showed the airplane about .3 miles the runway threshold at 200 ft msl and 73 kts groundspeed, on a heading of 209°. The Pilot’s Operating Handbook for the accident airplane model listed the minimum controllable airspeed as 82 knots indicated airspeed. Considering the wind information provided by air traffic control to the pilot of 090° at 10 knots, gusting to 14 knots, it is likely that the airplane’s airspeed likely decreased below its minimum controllable airspeed which resulted in a loss of control from which the pilot was not able to recover.

Probable cause

The pilot’s decision to operate the airplane with known maintenance discrepancies, which resulted in a total loss of right engine power. Contributing to the outcome was the pilot’s failure to maintain airspeed while returning to the airport with a single operating engine, which resulted in a loss of airplane control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24FA301
Event ID
20240711194672
Case number
ERA24FA301
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 3cfe5a61ae7db3d0a0025be1e2351604933bc4b88af3ae61aa99efc68588b30b; retrieved 2026-09-15T08:24:30.666Z.