FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA25FA187 · Mooney M20TN

26 Apr 2025 · Sparta, TN, United States

Mooney M20TN · Accident: loss of control in flight on approach

From Shelby County Airport (EET) to an unrecorded destination

Report a problem

Event

NTSB case
ERA25FA187
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
Ongoing
API-reported fatalities
3 · all aircraft and ground
Ground fatalities
Unknown
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

Mooney M20TN

Aircraft type
Mooney M20
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
N242RE
Operator
Unknown
Onboard fatalities
Unknown
Route
From Shelby County Airport (EET), Alabaster, ALTo not recorded
Aircraft age
About 18 years (built 2007)
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
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 control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

On April 26, 2025, about 1147 central daylight time, a Mooney M20TN, N242RE, was substantially damaged when it was involved in an accident near Sparta, Tennessee. The private pilot and two passengers were fatally injured. The airplane was operated as a Title 14?Code of Federal Regulations Part 91 personal flight.

Earlier that day the pilot flew from the Upper Cumberland Regional Airport (SRB), Sparta, Tennessee, to Shelby County Airport (EET), Alabaster, Alabama, where he landed, boarded 2 passengers and some cargo, then departed to return to SRB.

According to Federal Aviation Administration (FAA) preliminary air traffic control audio and Automatic Dependent Surveillance – Broadcast (ADS-B) data, after takeoff about 1039 the flight proceeded toward SRB while maintaining contact with several air traffic control facilities along the route of flight. Approaching SRB from the southwest, at 1136:55, the Sector 41 Radar Position controller of the Memphis Air Route Traffic Control Center instructed the pilot to cross the WENUB (intermediate fix/initial approach fix) at or above 4,000 ft and cleared the flight for the RNAV runway 4 approach to SRB. The flight continued direct to WENUB then turned to a northeast direction while flying toward SRB. At 1143:52, when the flight was about 6.2 nautical miles from the approach end of runway 4, the pilot cancelled his instrument flight rules clearance and informed the controller that the cloud bases were at 3,000 ft. Personnel at SRB reported hearing the pilot announce on the SRB common traffic advisory frequency that the flight was 11 miles and then 3 miles from SRB. There was no reported distress call made by the pilot.

The flight continued direct towards SRB until 1146:56, after which time a slight deviation to the right occurred. A witness who was located about .3 nautical mile west-northwest of the accident site reported there was, “some kind of trouble the engine was cutting in and out like it was out of gas.” She observed the airplane was in level flight then diverted her attention and then heard the sound of a crash.

During the final portion of the flight the airplane flew over a field with crop and impacted into trees and a creek about 1.5 nautical miles southwest from the approach end of runway 4. Initial examination of the engine revealed evidence of internal catastrophic malfunction. The No. 3 cylinder connecting rod was fractured and not attached at either end. The No. 3 cylinder connecting rod journal did not display any evidence of lack of lubrication. The engine was retained for further examination.

A Stratus 3 receiver was located in the wreckage and retained for read-out by the NTSB Vehicle Recorders Division. Additionally, the shoulder harness airbag electronic module assembly, a portion of the pitch trim system and an annunciator panel were also retained for further examination.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ERA25FA187
Event ID
20250426200069
Case number
ERA25FA187
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. 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: 903eb338dce4b953778f193e8a5550c25260e4c4e3adfe87850bc5fe8c07f514; retrieved 2026-09-15T09:04:16.734Z.