Cessna 402 accident near Easton, Maryland, July 16, 2024
On July 16, 2024 at about 1:32 pm local time, a 1973 Cessna 402, registered N7875E, was substantially damaged in an accident during maneuvering near Easton, Maryland. It was a positioning flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 16, 2024 · about 1:32 pm local time · cases in 2024
- Place
- Easton, Maryland · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 402 B, built 1973 · all 402s on the register
- Registration
- N7875E · registry record · serial 402B0432
- Damage
- Substantial damage
- Flight
- Positioning flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On July 16, 2024, about 0932 eastern daylight time, a Cessna 402B, N7875E, was substantially damaged when it was involved in an accident near Easton, Maryland. The airline transport pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 repositioning flight. According to the operator, the purpose of the accident flight was to reposition the airplane to Easton Airport (ESN), Easton, Maryland, to conduct future atmospheric testing flights. Two days prior to the accident flight, ground engine runs were performed by maintenance personnel at the conclusion of an annual inspection. Following the ground engine runs, the pilot stated to his manager that 12 gallons of fuel remained in each main (tip) fuel tank, and he was going to add 20 additional gallons to each main fuel tank so that he did not have to switch tanks during the upcoming flight to ESN (accident flight). However, airport security video showed that the pilot added 20 gallons of fuel to each auxiliary fuel tank, rather than the main fuel tanks. The airplane was not flown from the time of that fueling, to the accident flight. Review of preliminary information from the Federal Aviation Administration (FAA) revealed that the flight departed Tipton Airport (FME), Fort Meade, Maryland at 0857. The flight proceeded uneventfully toward ESN. About 0928, the pilot contacted the ESN air traffic control tower and reported a “pretty significant engine problem.” At that time, the airplane was about 12 miles southwest of ESN and the controller instructed the pilot to enter a right base leg of the airport traffic pattern for runway 15 and to report a 2-mile right base leg. About 1 minute later, the pilot reported that the airplane was at 2,400 ft mean sea level and setting up for a right base leg, with a “pretty bad right engine.” About 30 seconds later, the pilot declared an emergency and stated that both engines were losing power. The controller cleared the airplane to land on runway 15 via an approach from any direction; however, the pilot replied that he was not going to reach the airport and was going to try to land in a field. The airplane subsequently impacted the Tred Avon River about 4 miles southwest of ESN. The left wing, including left engine, separated about 1 ft outboard of the wing root and was not located. The remaining wreckage remained intact and was subsequently examined at a recovery facility. The cockpit remained intact. The pilot seat lapbelt and shoulder harness remained attached and were unfastened. The left engine controls were in the full forward position. The right engine controls were between mid-range and full forward. The right fuel selector handle was in the auxiliary fuel tank position and the left engine fuel selector handle was in the crossfeed position. The flap handle was in the 15° flap extended (approach flaps) setting. The landing gear was in the extended position. Flight control continuity was confirmed from the cockpit controls to the elevator, elevator trim, rudder, and rudder trim. Aileron control continuity for both wings was confirmed from the yoke to the nacelle area. Both right wing fuel tanks were breached during impact. The bottom sparkplugs were removed from the right engine and the propeller was rotated by hand. The sparkplug electrodes were intact and exhibited some corrosion consistent with water immersion. Water emanated from the sparkplug holes during rotation. Crankshaft, camshaft, and valve train continuity were confirmed to the rear accessory section of the engine. Both magnetos sparked at all leads when bench tested. The unmetered fuel line, from the engine driven fuel pump to the fuel metering valve, contained about 1/2 ounce of fuel. The fuel was blue, clear, and absent of any visible contamination. A few drops of fuel were recovered in the engine driven fuel pump and in the screen at the metering valve, but in total, less than 1 ounce of fuel was recovered from the right engine and its fuel system. The fuel nozzles, fuel manifold screen, and oil filter screen were absent of contamination. The pilot’s most recent FAA first-class medical certificate was issued on March 27, 2024. At that time, he reported a total flight experience of 4,100 hours, with 0 hours accrued during the preceding 6 months.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Fuel starvation during maneuvering defining event
- Loss of engine power (total) during maneuvering
- Off-field or emergency landing during emergency descent
- Ditching during emergency descent
The aircraft
- Airframe total time: 6,180 hours
- Last inspection: annual inspection, July 12, 2024; 1 hours since
- Maximum gross weight: 6,300 lb
- Seats: 3
- Landing gear: retractable
- Operator: University Research Foundation
The flight
- Departed from: FME Tipton MD at 12:57 pm
- Destination: ESN Easton MD
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 220° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 88°F (31°C), dew point 77°F (25°C)
- Altimeter: 29.87 inHg
- Observation at 9:32 am from ESN, 4 miles away
Weather report (METAR): KESN 161332Z 22006KT 10SM CLR 31/25 A2987
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Connections how this case links to the rest of the register
- N7875E on the register today · the tail number may have moved to another aircraft since
- Cessna 402 174 registered today · the model family and its accident history
- Cessna 72,674 aircraft on the register
- Fort Meade Executive · departed from
- Easton/Newnam Field · bound for
- Accidents and incidents in Maryland 837 since 1982 · 111 in the last ten years
- Maryland 2,352 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA24FA305.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.