CEN16LA008 · Beechcraft A36
Frog Air Beechcraft A36 · Accident: ground handling event while taxiing
From Dallas Love Field (DAL) to Rick Husband Amarillo International Airport (AMA)
Event
- NTSB case
- CEN16LA008
- 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
- 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
- Visual Meteorological Cond
Beechcraft 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
- N55674
- Operator
- Frog Air
- Onboard fatalities
- Unknown
- Route
- From Dallas Love Field (DAL), Dallas, TXTo Rick Husband Amarillo International Airport (AMA), Amarillo, TX
- Aircraft age
- About 25 years (built 1990)
- 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
- Taxi
- 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
- Ground handling event
- 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
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was taxiing for takeoff when he inadvertently turned onto a vehicle service road instead of the taxiway as he was leaving the ramp area. He then looked down to review the airport diagram on his tablet. As he was reviewing the airport diagram while still taxiing, the left wing impacted a fence post. The airplane's nose then turned left, and the front of the airplane impacted a vehicle gate, which resulted in substantial damage to the left wing.
Probable cause
The pilot’s improper navigation onto a vehicle service road while taxiing and his subsequent distraction while looking at an airport diagram, which led to the airplane impacting a fence post.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16LA008
- Event ID
- 20151013X91320
- Case number
- CEN16LA008
- 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: 98976c23ea415e5636df0d7c9c901727dce794199aa73e74c9155febb0b1f9d8; retrieved 2026-09-16T02:53:01.469Z.