CEN25LA291 · Matesi Eugene E LANCAIR 320
Matesi Eugene E LANCAIR 320 · Accident: loss of engine power (total) en route
From Mesa, AZ to an unrecorded destination
Event
- NTSB case
- CEN25LA291
- 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
- Event fatalities
- Unknown
- 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
- Not recorded
Matesi Eugene E LANCAIR 320
- Aircraft type
- Matesi Eugene LANCAIR 320
- 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
- N70337
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Mesa, AZTo not recorded
- Aircraft age
- Not recorded
- 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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
On July 27, 2025, about 2001 central daylight time, a Lancair 320 airplane, N70337, was substantially damaged when it was involved in an accident near Wink, Texas. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that the accident flight was to pick up the airplane that he had recently purchased in Mesa, Arizona. During the flight, he noticed that the fuel level in both main fuel tanks was dropping at a faster rate than expected and eventually indicated empty. A short time later, the engine began to run rough, and the pilot attempted to troubleshoot the engine issue, but was unsuccessful. The engine subsequently lost total power. The pilot declared an emergency and air traffic control directed him to the nearest airport near Wink. He realized that he would not make it to the airport, so he chose to conduct an off-field landing. During the landing, the airplane sustained substantial damage to the empennage and fuselage. Postaccident examination showed that the 10-gallon header tank was full of fuel, and fuel was found in the fuel line to the fuel manifold. The airplane was retained for further examination.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record CEN25LA291
- Event ID
- 20250728200645
- Case number
- CEN25LA291
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2025-07-28.
- API snapshot SHA-256: c12f6ffb89700032aea991187b7b93ca5a240b6039829354062e9d527692920c; retrieved 2026-09-16T20:08:32.467Z.