FTW90FA179 · Beech 58
Beech Aircraft Beech 58 · Accident: in flight collision with object during landing
From Beech Factory Airport (BEC) to an unrecorded destination
Event
- NTSB case
- FTW90FA179
- 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
- 1 · 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
- Instrument Meteorological Cond
Beech 58
- Aircraft type
- Beechcraft 58
- 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
- N5641D
- Operator
- Beech Aircraft
- Onboard fatalities
- Unknown
- Route
- From Beech Factory Airport (BEC), Wichita, KSTo 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
- Landing · aborted
- 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
- In flight collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Aborted landing, delayed
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPORT WAS EQUIPPED WITH AN NDB APPROACH WITH A MDA OF 774 FEET AGL AND AN INBOUND COURSE OF 270 DEGREES. WITNESSES WERE CONSISTENT WITH RECOLLECTIONS OF HEAVY RAIN AND CEILINGS OF 300- 400 FEET. THE AIRPLANE'S INITIAL DOWNWIND APPROACH WAS TO RUNWAY 25 AND RESULTED IN A GO-AROUND. THERE WAS NO EVIDENCE TO INDICATE THAT THE PILOT EXECUTED THE PUBLISHED MISSED APPROACH. DURING THE SECOND ATTEMPTED LANDING A WITNESS SAW THE AIRPLANE ABOUT 2/3 OF THE WAY DOWN RUNWAY 25 STILL AT AN EXCESSIVE SPEED PRIOR TO HEARING THE ENGINES ACCELERATE. A PASSENGER REPORTED THAT THE PILOT ATTEMPTED TO STOP BUT THEY WERE NOT SLOWING DOWN. THE AIRPLANE GOT AIRBORNE AND STRUCK THE AIRPORT BOUNDARY FENCE 129 FEET FROM THE END OF THE RUNWAY. IT SUBSEQUENTLY STRUCK TREES AND A HOUSE WHERE A POST IMPACT FIRE BEGAN. BOTH THE HOUSE AND AIRPLANE WERE CONSUMED BY THE FIRE.
Probable cause
THE PILOT'S FAILURE TO ATTAIN THE PROPER TOUCHDOWN POINT AND HIS DELAYED DECISION TO ABORT THE LANDING. FACTORS WERE THE WEATHER CONDITIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW90FA179
- Event ID
- 20001212X24268
- Case number
- FTW90FA179
- 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: a489af179470334a68a5ea7bdd7e7342de10fe9f1721f6471fb6ec95b8eddc51; retrieved 2026-09-21T02:13:22.669Z.