WPR10CA229 · Aviat Aircraft Inc A-1B
Aviat Aircraft Inc A-1B · Accident: collision with terrain/object (non-CFIT) during initial climb
From Mineral Canyon Strip (UT75) to Canyonlands Regional Airport (CNY)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR10CA229
- 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
Aviat Aircraft Inc A-1B
- Aircraft type
- Aviat A-1
- 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
- N200HY
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Mineral Canyon Strip (UT75), Moab, UTTo Canyonlands Regional Airport (CNY), Canyonlands Fie, UT
- 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
- Initial climb
- 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
- Collision with terrain/object (non-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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the accident occurred during a mountain flying familiarization flight from an airport having a field elevation of 3,900 feet mean sea level. At the time of the pilot's takeoff from runway 32, which was 2,000-feet-long and 40-feet-wide, the wind was from 020 degrees at 10 to 15 knots. The pilot indicated that after liftoff, while the airplane was still in ground effect, he failed to maintain a flight track over the runway's centerline. The airplane drifted left, its left wing tip impacted bushes adjacent to the runway, and the airplane came to rest with a bent fuselage and ripped wing skins. The pilot indicated that the accident would have been prevented had he adequately compensated for the crosswind condition.
Probable cause
The pilot's inadequate crosswind compensation resulting in a loss of directional control and impact with bushes.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10CA229
- Event ID
- 20100507X25043
- Case number
- WPR10CA229
- 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: 9b3bb2f7eb67d2ad92836278e581dc137bcbb47bcf0fcdd4b2b2a29c5f59b9d3; retrieved 2026-09-15T14:00:43.648Z.