CEN14CA533 · Aviat Aircraft Inc PITTS S 2B B
Aviat Aircraft Inc PITTS S 2B B · Accident: loss of control in flight during landing
From Moriarty Municipal Airport (0E0) to Grants-Milan Municipal Airport (GNT)
Event
- NTSB case
- CEN14CA533
- 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 PITTS S 2B B
- Aircraft type
- Aviat PITTS S 2B
- 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
- N9YH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Moriarty Municipal Airport (0E0), Moriarty, NMTo Grants-Milan Municipal Airport (GNT), Grants, NM
- Aircraft age
- About 18 years (built 1996)
- 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
- 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
- Loss of control in flight
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was hired to reposition the airplane for the owner. According to the owner who spoke with the pilot, during the landing, the pilot encountered gusty winds which caused him to lose airplane control and impact terrain adjacent to the runway. The airplane sustained substantial damage to the right wing spar. The owner stated that there were no preaccident mechanical anomalies with the airplane that would have precluded normal operation.
The airplane owner completed the Pilot/Operator Accident Report (National Transportation Safety Board [NTSB] Form 6120.1), as the owner reported the pilot was uncooperative since the accident. The substantial damage to the airplane was reported to the NTSB on December 9, 2014, after a detailed inspection of the airplane damage was performed.
Probable cause
The pilot's failure to maintain control of the airplane during landing in gusty wind conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14CA533
- Event ID
- 20141209X43003
- Case number
- CEN14CA533
- 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: 747dab4427e0070b1d444525b4622855410e3c2b9340af34fccfc855a84a4d46; retrieved 2026-09-16T01:58:22.976Z.