ERA26LA180 · Piper Aircraft Inc PA-28-181
Piper Aircraft Inc PA-28-181 · Accident: loss of engine power (total) en route
From Palm Beach County Park Airport (LNA) to Melbourne Orlando International Airport (MLB)
Event
- NTSB case
- ERA26LA180
- 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 Aircraft Inc PA-28-181
- 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
- N643FT
- Operator
- Florida Institute of Technology
- Onboard fatalities
- Unknown
- Route
- From Palm Beach County Park Airport (LNA), Lantana, FLTo Melbourne Orlando International Airport (MLB), Melbourne, FL
- Aircraft age
- About 13 years (built 2013)
- 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
- Loss of engine power (total)
- 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 April 18, 2026, about 2115 eastern daylight time, a Piper PA-28-181, N643FT, was substantially damaged when it was involved in an accident near Indiantown, Florida. The private pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. According to the pilot, the purpose of the flight was to perform a night flight to a non-towered airport, then return to the departure airport, as part of his flight training curriculum. He arrived at Melbourne Orlando International Airport (MLB), Melbourne, Florida, around 1400 to plan the flight. The flight plan was completed then reviewed by the flight school’s dispatch staff. About 1915, the pilot performed a preflight inspection of the airplane and did not observe any anomalies. Based on the electronic fuel gauges and by visual inspection of the fuel tanks, the pilot determined he had full fuel; however, he separately reported 40 gallons (the airplane’s total fuel capacity was 50 gallons). He then started the engine, taxied the airplane to the active runway and performed an engine runup. The engine runup was normal and included a check of the magnetos and carburetor heat functionality. The pilot departed from MLB at 1941 and landed at Palm Beach County Park Airport (LNA), West Palm Beach, Florida, after an uneventful flight, about 2045. The pilot taxied back to runway 10 and departed at 2051, for the return flight to MLB. After departure, he maneuvered to the west to avoid nearby controlled airspace and then proceeded northbound. He climbed to 3,500 ft above mean sea level (msl) then performed the cruise checklist. About 25 minutes after departure, the airplane experienced a loss of engine power. The pilot reported that the engine rpm suddenly decreased from 2,600 to 800. He attempted to troubleshoot but was unable to restart the engine. The pilot stated that he thought he changed the fuel tanks after the loss of engine power, but that he “could be wrong.” He then declared “mayday” to air traffic control, secured the engine and prepared for a forced landing. The pilot initially attempted to divert to a nearby airport but determined that the airplane could not reach the airport and then prepared for an off-airport landing on a road. Shortly before landing, the pilot noticed cars driving on the road. The airplane subsequently touched down in a marsh, nosed over and came to rest inverted. The pilot exited the airplane through a window. A postaccident examination of the airplane by an FAA inspector found substantial damage to the empennage and fuselage. The inspector “rocked” the wings of the airplane and heard liquid sloshing back and forth in both fuel tanks, but was unable to open the tanks due to the position of the airplane. First responders noted fluid leaking from both wings. The wreckage was recovered and retained for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ERA26LA180
- Event ID
- 20260420202852
- Case number
- ERA26LA180
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2026-04-19.
- API snapshot SHA-256: 12cfb2f2392e57cca393d8673b5bfd74f613912b6e41c7866c97da25674cab83; retrieved 2026-09-16T21:17:22.160Z.