BFO94LA150 · Beech 36
Beech 36 · Accident: on ground/water collision with object during landing
From McGhee Tyson Airport (TYS) to Delaware Coastal Airport (GED)
Event
- NTSB case
- BFO94LA150
- 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
Beech 36
- Aircraft type
- Beechcraft 36
- 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
- N15512
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From McGhee Tyson Airport (TYS), Knoxville, TNTo Delaware Coastal Airport (GED), DE
- 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 · landing roll
- 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
- On ground/water 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
- Substantial
Cause areas
- Notams › Inaccurate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING THE LANDING ROLL ON RUNWAY 22, THE PILOT NOTICED AN OBSTRUCTION (ROW OF RAILROAD TIES) THAT HAD BEEN PLACED ON THE RUNWAY AS A CONSTRUCTION BARRIER. SHE APPLIED BRAKES, BUT WAS UNABLE TO STOP THE AIRPLANE BEFORE IT COLLIDED WITH THE BARRIER. AN FAA INSPECTOR STATED THE AIRPLANE HAD TOUCHED DOWN ABOUT 3000 FEET DOWN THE 5000 FOOT LONG RUNWAY. THE CONSTRUCTION BARRIER WAS LOCATED 1250 FEET FROM THE DEPARTURE END OF THE RUNWAY GIVING IT AN EFFECTIVE LENGTH OF 3750 FEET. A NOTAM STATED ONLY THAT THE THRESHOLD FOR RUNWAY 4 WAS DISPLACED 1250 FEET. THE PILOT HAD OBTAINED A WEATHER BRIEFING FOR AN IFR FLIGHT, BUT STATED THAT SHE DID NOT RECEIVE NOTAM INFORMATION ABOUT THE DESTINATION AIRPORT. ALSO, SHE SAID THAT THERE WERE NO DISPLACED THRESHOLD MARKINGS AND THAT SHE WAS UNABLE TO SEE ANY OBSTRUCTION FROM THE AIR.
Probable cause
THE ISSUANCE OF A NOTAM WITH INADEQUATE INFORMATION. FACTORS RELATED TO THE ACCIDENT WERE: THE PILOT'S FAILURE TO ATTAIN THE PROPER TOUCHDOWN POINT, AND THE LACK OF VISUAL CUES CONCERNING THE CONSTRUCTION BARRIER.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO94LA150
- Event ID
- 20001206X01973
- Case number
- BFO94LA150
- 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: d8c285913f1f1c6582eb2af61235c47aed8d58dbfd2ecc97a38c8dc3f9bb161a; retrieved 2026-09-23T00:46:10.422Z.