DEN05CA062 · Beech A36
Mesa Pilot Development Beech A36 · Accident: loss of control in flight during initial climb
From Four Corners Regional Airport (FMN) to Four Corners Regional Airport (FMN)
Event
- NTSB case
- DEN05CA062
- 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
- N435P
- Operator
- Mesa Pilot Development
- Onboard fatalities
- Unknown
- Route
- From Four Corners Regional Airport (FMN), Farmington, 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
- Initial climb
- 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
- Loss of control in flight
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Stall
- 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 › Aircraft control, not maintained
- Dual student › Airspeed, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight instructor stated that his student was performing a short-field takeoff on runway 25. He stated that once the airplane became airborne, he "noted that the pitch was a bit high." He stated that the pitch continued to increase and the airplane rolled to the right and then to the left. The instructor stated that he took control of the airplane and decreased the angle of attack and rolled the wings level. The airplane continued to descend and impacted the left side of the runway, bouncing several times, causing substantial damage. According to the METAR (aviation routine weather report) taken at 1353, the winds were reported as 220 degrees at 13 knots, gusting to 17 knots.
Probable cause
the student pilot's failure to maintain airspeed which resulted in a stall and loss of control. Contributing factors were wind gusts, instructor's delay in taking remedial action, and the instructor's inadequate supervision of the flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN05CA062
- Event ID
- 20050414X00453
- Case number
- DEN05CA062
- 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, 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: b2e2e85cb944aab12eddc8a256df2e98c3d44fd6ceb9d7a2a2377ff362dc63d1; retrieved 2026-09-22T06:11:27.633Z.