GAA16CA362 · Cessna U206 G
United States Department of Interior Cessna U206 G · Accident: abnormal runway contact during landing
From Boise Air Terminal/Gowen Field (BOI) to Ely Airport Yelland Field (ELY)
Event
- NTSB case
- GAA16CA362
- 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
- Government
- 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 U206 G
- 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
- N9304R
- Onboard fatalities
- Unknown
- Route
- From Boise Air Terminal/Gowen Field (BOI), Boise, IDTo Ely Airport Yelland Field (ELY), Ely, NV
- Aircraft age
- About 32 years (built 1984)
- 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
- Public Aircraft
- 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
- Landing · flare/touchdown
- 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
- Abnormal runway contact
- 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
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that during a public-use flight in a single-engine airplane, he was providing instruction to an airline transport pilot who was only rated for multi-engine airplanes. The flight instructor further reported that the pilot receiving instruction was the pilot flying and was "fast" on final approach. During the landing flare, the airplane ballooned and bounced once. After the bounce, the flight instructor applied aft flight control pressure because he believed the airplane was going to touch down nose wheel first. The subsequent landing roll was completed without further incident.
After loading additional passengers, the flight instructor completed the return flight to their domicile without further incident. During a post-flight inspection damage was found to the tail hook and aft fuselage area.
Further inspection revealed that the airplane sustained substantial damage to the aft bulkhead, which was likely the result of a tail strike during the bounced landing during the previous flight. The flight instructor reported that he did not hear the tail strike during the bounced landing and he did not inspect the empennage before departing for the terminating destination.
The flight instructor did not report any mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The flight instructor's incorrect pitch control during the landing flare, which resulted in a tail strike.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA362
- Event ID
- 20160706X01743
- Case number
- GAA16CA362
- 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: 408c948a65fdedd2438f5581a6261ecf6e17d03180d1b9b7283e377a53c53ae6; retrieved 2026-09-16T03:37:19.011Z.