DEN06LA035 · Beech A36
Beech A36 · Accident: hard landing
From Four Corners Regional Airport (FMN) to Four Corners Regional Airport (FMN)
Event
- NTSB case
- DEN06LA035
- 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
Beech A36
- Aircraft type
- Beechcraft 36
- 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
- N1830V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Four Corners Regional Airport (FMN), Farmnington, NMTo Four Corners Regional Airport (FMN), Farmington, 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
- Dual student › Flare, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot in the left seat was working on his commercial pilot certificate, and was receiving instruction from the flight instructor in night takeoffs and landings. On the first landing attempt, the approach and landing speed "looked good" to the instructor. "[The] pilot apparently did not flare sufficiently to avoid [a] hard landing and bounce." The instructor took control of the airplane and brought it to a full stop. One additional takeoff and full stop landing was made by the pilot receiving instruction. The airplane was then secured for the night. The damage was discovered the next morning by another pilot performing a preflight inspection.
Probable cause
the student pilot's improper flare, resulting in a hard landing. Contributing factors were the flight instructor's inadequate supervision of the pilot, and the dark night light conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN06LA035
- Event ID
- 20060130X00131
- Case number
- DEN06LA035
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2006-01-26.
- API snapshot SHA-256: ba4cd2fd765729eb356387df684f42b6ef9d29256caa17765ccaf13d8f9912e3; retrieved 2026-09-22T05:08:30.262Z.