CEN10FA069 · Beech A36
Beech A36 · Accident: controlled flight into terrain/object (CFIT) on approach
From Kerrville / Kerr County Airport at Louis Schreiner Field (KERV) to Maverick County Memorial International Airport (5T9)
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN10FA069
- 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
- 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
- Instrument Meteorological Cond
Beech A36
- 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
- N1105N
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kerrville / Kerr County Airport at Louis Schreiner Field (KERV), Kerrville Muni, TXTo Maverick County Memorial International Airport (5T9), Eagle Pass, TX
- 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 final approach
- 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
- Controlled flight into terrain/object (CFIT)
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While on an instrument approach to the non-towered airport, the airplane collided with the airport's perimeter fence and terrain. The fence and perimeter road were parallel to, and about 750-feet east of the runway. The last radar plot was at an altitude of 1,200 feet MSL (Mean Sea Level), but slightly east of the runway, and approximately 435 feet from the accident site. About 30 minutes after the accident, deputies reported that the weather was "foggy". The instrument approach that the pilot was following was the RNAV (GPS) 31. The published minimums for this instrument approach are a 400-foot ceiling and one-mile visibility. The automated weather station about 33 miles northwest of the accident site reported at 0552, calm winds, temperature 41 degrees Fahrenheit, dew point 41 degrees Fahrenheit, visibility less than 1/4 miles (and a Runway visual range ( RVR) of 600 feet variable to 1200 feet) in fog and an indefinite ceiling, altimeter pressure setting 29.85 inches of Mercury. An examination of the airplane failed to reveal any anomalies with the airframe, structure, or systems. The airplane's engine was removed from the airframe and placed in an engine test facility. An engine test run was conducted and the engine was able to produce rated horsepower, without hesitation or interruption. Under the conditions at the time, the pilot appeared to have mistaken the east perimeter road for the runway landing point.
Probable cause
The pilot's decision to continue the approach below minimums without visual references, and subsequent collision with the perimeter fence/terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10FA069
- Event ID
- 20091209X94124
- Case number
- CEN10FA069
- 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: 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: 4f55975cfcfb95f894cf509bbdfe9c52232f21c853f823f1d0d734798c4b52c0; retrieved 2026-09-13T20:35:28.571Z.