WPR14CA047 · Aviat Aircraft Inc A 1B B
Aviat Aircraft Inc A 1B B · Accident during landing
From Vance Brand Airport (LMO) to LaGrange, WY
Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- WPR14CA047
- 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 B
- 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
- N510MA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Vance Brand Airport (LMO), Longmont, COTo LaGrange, WY
- Aircraft age
- About 8 years (built 2005)
- 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 · landing roll
- 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
- Miscellaneous/other
- 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
The pilot reported that after touchdown on the grass/sod airstrip, the landing roll was normal for about 100 feet, but then the airplane came to an abrupt stop, like it had hit something. The airplane nosed over substantially damaging the rudder and wings.
The pilot and ranch personnel inspected the landing area and followed the airplane's tracks back toward the point of touchdown. They found a large hole, likely dug by an animal, approximately 24" deep, and in line with the airplane's right tire track. The pilot said he did not see the hole when flying downwind, nor on the base leg, or final approach.
The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's decision to land on a rough surface with hidden obstructions (holes).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR14CA047
- Event ID
- 20131109X05102
- Case number
- WPR14CA047
- 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: ee95e61bfcf3166e13655be3c8f700dc6663aeb261abacfb8086938b846ff365; retrieved 2026-09-15T23:05:42.838Z.