DEN00LA081 · Hutchins RV4
Hutchins RV4 · Accident: hard landing
From 2V1 · Pagosa Springs, CO to Los Alamos Airport (LAM)
Event
- NTSB case
- DEN00LA081
- 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
- 0
- 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
Hutchins RV4
- Aircraft type
- Hutchins RV4
- 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
- N724CF
- Operator
- Marilyn J. Hutchins · private individual
- Onboard fatalities
- Unknown
- Route
- From 2V1 · Pagosa Springs, COTo Los Alamos Airport (LAM), NM
- 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
- Landing · flare/touchdown
- First occurrenceThe 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
- Hard landing
- 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
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During approach for landing at the completion of a cross-country flight, the pilot noted the UNICOM reported the wind was calm but the windsock stuck straight out. During the landing attempt, the aircraft bounced and as it departed the side of the runway into dirt the pilot attempted to abort the landing. After a climb was initiated, a steep bank was made to avoid striking the airport perimeter fence. The aircraft then settled, in a wings level attitude, onto the ground causing the main landing gear to collapse and substantial damage to the airframe. The pilot reported the wind as variable at 10 knots with no gusts. Density altitude at the time was approximately 9,600 feet.
Probable cause
The pilot's failure to maintain control of the aircraft after initiating a go-around following a hard bounced landing. Factors were variable shifting winds and a high-density altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN00LA081
- Event ID
- 20001212X20805
- Case number
- DEN00LA081
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 21aa3bfebb5cb4d5ed5ffcb184e613c230feeee0abd5da8a7994f6a3114c3536; retrieved 2026-09-22T12:56:37.469Z.