FTW93LA243 · Boeing A75N1
Boeing A75N1 · Accident: total loss of engine power (mechanical failure) while maneuvering
From an unrecorded airport to Lafayette Regional Airport (LFT)
Event
- NTSB case
- FTW93LA243
- 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
- Completed
- 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
Boeing A75N1
- Aircraft type
- Boeing A75
- 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
- N450EC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Lafayette Regional Airport (LFT)
- 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
- Maneuvering
- First occurrenceThe 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
- Total loss of engine power (mechanical failure)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Reason for occurrence undetermined
Approximate · Estimated position: the centre of Lafayette, LA, the place the record names. Not the accident site.
NTSB narrative
A COMPLETE POWER LOSS WAS EXPERIENCED DURING A PRACTICE FLIGHT AS THE AIRPLANE WAS FLYING A LOW PASS DOWN A RUNWAY WITH A WING WALKER STRAPPED TO THE UPPER WING. THE PILOT STATED THAT HE COULD NOT MANEUVER BACK TO THE RUNWAY AND HE EXECUTED A FORCED LANDING INTO A WOODED RESIDENTIAL AREA. HE ATTEMPTED TO LAND IN THE TOPS OF THE TREES; HOWEVER, THE AIRPLANE FEEL NOSE FIRST TO THE GROUND. THE PILOT REPORTED THAT THE ENGINE FAILURE WAS CAUSED BY A FAILED FUEL PUMP, BUT HE DID NOT SUBMIT THE PUMP FOR EXAMINATION. THE WING WALKER, STATED THAT THE POWER LOSS WAS A RESULT OF FUEL EXHAUSTION. ON SCENE EXAMINATION OF THE WRECKAGE BY THE FAA REVEALED SOME FUEL IN THE TANK AND FUEL SPILLAGE AROUND THE ACCIDENT SITE.
Probable cause
THE ENGINE FAILURE FOR UNDETERMINED REASONS. A FACTOR WAS THE LACK OF SUITABLE TERRAIN ONTO WHICH A FORCED LANDING COULD BE EXECUTED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW93LA243
- Event ID
- 20001211X13158
- Case number
- FTW93LA243
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 82db9ae27bdb224fbd9dd657ba864d83bc19721303b7c718eae7758975b4017c; retrieved 2026-09-21T14:10:23.377Z.