BFO94FA103 · Beech A-36
Duncan Aviation Inc. & T.Hayes Beech A-36 · Accident: in flight collision with terrain/water on approach
From Lincoln Airport (LNK) to an unrecorded destination
Event
- NTSB case
- BFO94FA103
- 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
- 3 · 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 A-36
- Aircraft type
- Beechcraft A-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
- N1525G
- Operator
- Duncan Aviation Inc. & T.Hayes
- Onboard fatalities
- Unknown
- Route
- From Lincoln Airport (LNK), Lincoln, NETo 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
- Approach · IFR missed approach
- 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 terrain/water
- 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 › IFR procedure, not followed
- Pilot in command › Proper altitude, not obtained/maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE WAS ON AN IFR FLIGHT PLAN. PRIOR TO THE APPROACH, THE PILOT TOLD ATC THAT HE 'NEEDED ALL THE HELP I CAN GET. I'M KIND OF NEW AT THIS.' HE WAS THEN CLEARED TO DESCEND AND BEGAN RECEIVING RADAR VECTORS FOR THE ILS APPROACH. THE AIRPLANE BEGAN TO HEAD TOWARDS A NEARBY VOR AFTER BEING VECTORED TO THE LOCALIZER COURSE. THE PILOT RADIOED THAT HE WAS NOT ON THE LOCALIZER AND REQUESTED ASSISTANCE. ATC PROVIDED ANOTHER VECTOR AND CLEARED THE AIRPLANE FOR THE APPROACH. THE AIRPLANE INTERCEPTED THE LOCALIZER AND THEN DISAPPEARED FROM RADAR. RADIO COMMUNICATION WAS LOST AFTER THE PILOT DECLARED A MISSED APPROACH. THE AIRPLANE IMPACTED TERRAIN SOUTH OF THE AIRPORT. THE PILOT HAD RECEIVED HIS INSTRUMENT RATING 6 MONTHS BEFORE THE ACCIDENT. SEVERAL PROCEDURES SPECIFIED IN THE ATC HANDBOOK WERE NOT FOLLOWED BY THE CONTROLLER. AFTER THE PILOT INITIALLY BEGAN TO STRAY FROM THE LOCALIZER COURSE, HE WAS NOT INFORMED OF HIS POSITION RELATIVE TO THE LOCALIZER, NOR WAS AN INQUIRY MADE AS TO THE PILOT'S INTENTIONS. IN ADDITION, THE VECTOR PROVIDED TO INTERCEPT THE LOCALIZER COURSE RESULTED IN AN INTERCEPT ANGLE OF 40 DEG; THE ATC HANDBOOK STIPULATES A MAXIMUM INTERCEPT ANGLE OF 30 DEG.
Probable cause
THE PILOT'S FAILURE TO FOLLOW THE PUBLISHED MISSED APPROACH PROCEDURE, AND HIS FAILURE TO OBTAIN AND/OR MAINTAIN ADEQUATE ALTITUDE TO AVOID COLLISION WITH THE TERRAIN. FACTORS IN THE ACCIDENT WERE: THE PILOT'S LACK OF INSTRUMENT FLYING EXPERIENCE, AND THE CONTROLLER'S FAILURE TO FOLLOW STANDARD PROCEDURES AND TO PROVIDE MORE COMPLETE AND HELPFUL GUIDANCE TO THE INEXPERIENCED PILOT DURING THE APPROACH.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO94FA103
- Event ID
- 20001206X01446
- Case number
- BFO94FA103
- 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: f082498a5dedbbab8ea7419fef64464e35da77eeb584414f675d697307707b62; retrieved 2026-09-21T00:07:01.321Z.