ERA26LA127 · Piper PA-28-151
JKG Piper PA-28-151 · Accident: off-field or emergency landing en route
From McKellar-Sipes Regional Airport (MKL) to City of Murfreesboro Airport (MBT)
Event
- NTSB case
- ERA26LA127
- 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
- 0 · 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
Piper PA-28-151
- Aircraft type
- Piper PA-28
- 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
- N85RW
- Operator
- JKG
- Onboard fatalities
- Unknown
- Route
- From McKellar-Sipes Regional Airport (MKL), jackson, TNTo City of Murfreesboro Airport (MBT), Murfreesboro, TN
- Aircraft age
- About 50 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
- En route
- 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
- Off-field or emergency landing
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On February 24, 2026, about 1107 central standard time, a Piper PA-28-151, N85RW, was substantially damaged when it was involved in an accident near Arno, Tennessee. The pilot was not injured. The airplane was operated as a 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that the purpose of the cross-country flight was to build experience in preparation for his commercial pilot’s certificate. During the preflight inspection, he visually confirmed the fuel level was “to the tabs” in the fuel tanks, which equated to 40 gallons of fuel and noted that the electronic fuel gauges indicated the same quantity. After completing the before takeoff checks, he departed for Murfreesboro Municipal Airport (MBT), Murfreesboro, Tennessee. Preliminary ADS-B data obtained from the FAA showed the airplane departed about 0827, climbed to a cruising altitude of 4,200 ft, then descended and landed at Jackson Regional Airport (MKL), Jackson, Tennessee, about 1005. The pilot stated that after landing, he taxied back to the active runway, without shutting down the airplane, for the return flight to MBT. The pilot estimated that about 10-15 gallons of fuel remained in each of the two wing tanks before departure. He completed his takeoff checklist and departed for MKL. ADS-B data showed that after departure at 1013, the airplane climbed on a southwesterly heading to a cruising altitude of about 7,000 ft, where it remained for 35 minutes. The pilot reported about 36 minutes before arrival at his destination, he felt the airplane’s “controls vibrating.” The pilot suspected carburetor ice and applied carburetor heat. He subsequently noticed the engine sputtering and the engine gauges “going back and forth.” He observed the fuel gauges for each wing tank indicate from 0 to 10 gallons, then back to 0. He also reported that the engine oil temperature and pressure gauges began to decrease, followed by total loss of engine power. He turned on the electric fuel pump and rotated the fuel selector from the left fuel tank to the right fuel tank. The engine restarted but then lost all power about a minute later. He returned the fuel selector to the left tank, but the engine did not restart. The pilot declared an emergency with air traffic control. Unable to reach a nearby airport, he selected a field for an off-airport landing. The last ADS-B data point at 1107 showed the airplane, at 825 ft above mean sea level (msl) and descending at 896 ft per minute. The airplane impacted trees at the edge of a field and came to a rest on the edge of a hill. A postaccident examination of the airplane by an FAA inspector revealed substantial damage to the fuselage, empennage and wings. The wings separated from the fuselage at the wing roots and remained partially suspended in trees. Both wings sustained leading edge damage, scrapes, multiple punctures, broken fuel lines and were absent of fuel. The engine oil level gauge revealed about 4 quarts of oil in the engine at the time of recovery. The fuel strainer was observed displaced aft, consistent with impact damage, and found absent of fuel. The wreckage was retained for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA26LA127
- Event ID
- 20260224202497
- Case number
- ERA26LA127
- 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. 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: 37f18752017288ed77108d61cda34cb91c1175c8f0fdb993d975c50c629eb9a5; retrieved 2026-09-16T20:50:17.244Z.