GAA15CA174 · Pilatus PC12 45
Montana Aircraft Pilatus PC12 45 · Accident: tailstrike during landing
From Bozeman Yellowstone International Airport (BZN) to Bozeman Yellowstone International Airport (BZN)
Event
- NTSB case
- GAA15CA174
- 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
Pilatus PC12 45
- Aircraft type
- Pilatus PC12
- 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
- N220CL
- Operator
- Montana Aircraft
- Onboard fatalities
- Unknown
- Route
- From Bozeman Yellowstone International Airport (BZN), Belgrade, MTTo Bozeman Yellowstone International Airport (BZN), Belgrade, MT
- Aircraft age
- About 14 years (built 2001)
- 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
- 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
- Tailstrike
- 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
During a pilot competency checkride, while on downwind in the traffic pattern, the pilot reported that the examiner requested a zero flap, power off, 180 degree approach and landing. As the airplane arrived at the threshold, the pilot noted higher than normal airspeed and a greater than normal approach angle of attack. The pilot increased the angle of attack until the stick shaker activated and then performed a go around maneuver. During the go around, the tail struck the runway, but the pilot reported that he did not remember feeling the tail touch the runway. After the go around, the pilot completed the maneuver without incident. The airplane sustained substantial damage to the rudder during the tailstrike.
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 improper use of pitch control during an instructional maneuver, which resulted in a tail strike during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA15CA174
- Event ID
- 20150709X90721
- Case number
- GAA15CA174
- 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: 3dc923986b3763c0e3c61c130db76d3aa5355066c791e1a338fa6c702aae7a11; retrieved 2026-09-16T02:31:03.905Z.