FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10CA018 · Cessna T206H

16 Oct 2009 · Johnson City, KS, United States

Cessna T206H · Accident: controlled flight into terrain/object (CFIT) on approach

From Greeley–Weld County Airport (KGXY) to Stanton County Municipal Airport (K2K3)

Report a problem

Event

NTSB case
CEN10CA018
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 T206H

Aircraft type
Cessna 206
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
N454TG
Operator
Jackie L Bugg · private individual
Onboard fatalities
Unknown
Route
From Greeley–Weld County Airport (KGXY), Greeley, COTo Stanton County Municipal Airport (K2K3), Johnson City, KS
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 · VFR pattern final
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
Substantial

Cause areas

  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

As the pilot was on final approach to Runway 17 during the night visual-flight-rules flight, the airplane entered a fog bank approximately 50 feet off of the ground and he lost all visual reference. The pilot applied full throttle to go around, but not in time to arrest the descent. The airplane impacted the ground short of the runway and nosed over, resulting in substantial damage to the airplane. The pilot reported no mechanical anomalies with the airplane prior to the accident.

Probable cause

The pilot's delayed action in applying full power during a go-around after flying into a fog bank.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10CA018
Event ID
20091017X63854
Case number
CEN10CA018
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. 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: 84dc9d8b19a37796d0ec471764342a0f37610a8b014249444028a29f2d753e41; retrieved 2026-09-15T13:25:01.254Z.