CEN20LA272 · Golden Circle Air T-Bird TBT-06
Golden Circle Air T-Bird TBT-06 · Accident: low altitude operation/event while maneuvering
From Grosse Ile Municipal Airport (ONZ) to an unrecorded destination
Event
- NTSB case
- CEN20LA272
- 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
- Visual Meteorological Cond
Golden Circle Air T-Bird TBT-06
- Aircraft type
- Golden Circle Air T-BIRD
- 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
- N50JH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Grosse Ile Municipal Airport (ONZ), Grosse Ile, MITo not recorded
- Aircraft age
- About 11 years (built 2009)
- 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
- Maneuvering · low-altitude flying
- 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
- Low altitude operation/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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Experience/knowledge
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A witness saw the noncertificated pilot take off downwind on a taxiway; once airborne, the airplane drifted to the right, struck a taxiway marker light, then continued its departure to the south. Strong gusting wind conditions out of the northwest had been reported throughout the day. About 40 minutes later, another witness located about 2 miles north of the airport saw the airplane flying southbound about 300 and 400 ft above ground level (agl). A third witness located near the accident site about 1/2 mile south of the airport saw the airplane flying about 200 to 300 ft agl over a residential area; this witness reported that it appeared the pilot was having difficulty gaining altitude and maintaining a stable attitude due to the gusting wind conditions. Subsequently, the airplane struck a tree in a residential neighborhood and impacted the ground. The airplane came to rest inverted beneath the tree, and both wings and the fuselage were crushed aft. Postaccident examination revealed that the pilot's control stick was dislodged from the socket that connected it to the control system. The retaining bolt that should have held the stick in the socket was missing. The bolt holes showed no signs of deformation or stress, indicating that the bolt was not installed when the airplane impacted the ground. Given that the witness observations were consistent with the pilot having control of the airplane before impact with the tree, it is unlikely that the control stick separated in flight, rather, it is likely the control stick was dislodged during the impact sequence. There were no other mechanical anomalies found with the airframe or engine that would have precluded normal operations. The pilot did not hold a pilot certificate, and no evidence was found that he had received any formal flight training. According to a family member, this was likely the pilot’s second or third flight in the airplane.
Postmortem toxicology testing detected the stimulant amphetamine at blood concentrations associated with abuse, the impairing anti-anxiety medication diazepam and its metabolites within therapeutic range, and the antidepressant citalopram at subtherapeutic levels. These medications and the associated medical conditions for which they are prescribed can negatively impact judgment and psychomotor performance. The pilot, however, was very inexperienced and did not appear to have the skills to safely operate the airplane, especially considering the gusting wind conditions. Given his lack of skills and experience, it is difficult to determine what role, if any, his medication use or medical conditions had on his inability to safely fly the airplane. Thus, this investigation was unable to determine whether the effects of the pilot’s use of amphetamine, diazepam, and citalopram were factors in this accident.
Probable cause
The noncertificated pilot’s failure to maintain clearance from trees while maneuvering at low altitude in gusting wind conditions. Contributing to the accident was the pilot’s lack of flight experience.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20LA272
- Event ID
- 20200711X82324
- Case number
- CEN20LA272
- 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, coordinates, cause areas. 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: 2f34211103d9670b5ae7e3c8bbd31faa984d1ec37b1d739d319e7e63495759e3; retrieved 2026-09-15T07:17:12.294Z.