GAA16CA034 · Cessna 182R
Brentco Aerial Patrol Cessna 182R · Accident: airport occurrence while taxiing
From Granbury Regional Airport (GDJ) to Granbury Regional Airport (GDJ)
Event
- NTSB case
- GAA16CA034
- 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
Cessna 182R
- Aircraft type
- Cessna 182
- 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
- N9736H
- Operator
- Brentco Aerial Patrol
- Onboard fatalities
- Unknown
- Route
- From Granbury Regional Airport (GDJ), Granbury, TXTo Granbury Regional Airport (GDJ), Granbury, TX
- Aircraft age
- About 34 years (built 1981)
- 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
- Airport occurrence
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Pole
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was taxiing on the ramp after landing and had looked to his left at the line serviceman that was "marshalling" him and the right wing struck a fence post. The airplane sustained substantial damage to the right wing and fuselage.
The line serviceman reported that he was standing in the location where he wanted the pilot to park the airplane, with his arms raised to get the pilot's attention. The line serviceman reported that he was not giving the pilot hand signals to direct him on the ramp at the time of the accident.
The pilot reported no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
Probable cause
The pilot's diverted attention while taxiing, which resulted in a collision with a fence post.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA034
- Event ID
- 20151029X61656
- Case number
- GAA16CA034
- 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: bf20c728ea3cb6b8d51b808238ce67929ed33e0323cb13d474971d23fc41e8d0; retrieved 2026-09-16T02:56:11.475Z.