FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX06CA194 · Cessna T207A

2 Jun 2006 · Jean, NV, United States

Cessna T207A · Accident: loss of control in flight during initial climb

From 07L · Jean, NV to an unrecorded destination

Report a problem

Event

NTSB case
LAX06CA194
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

Cessna T207A

Aircraft type
Cessna 207
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
N9962M
Operator
Unknown
Onboard fatalities
Unknown
Route
From 07L · Jean, NVTo not recorded
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/mush
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 › Airspeed, not obtained/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 airplane failed to gain altitude and settled into the ground during the takeoff initial climb. The firewall buckled during the ground contact. The pilot said that just after takeoff, the airspeed decreased to 60 knots and the airplane was 300 feet above ground level. He was unable to recover the airspeed and he touched down in a field. The pilot noted that the temperature was over 100 degrees Fahrenheit and the wind was from the west at 10 knots and gusting. The pilot said that there were no mechanical failures or malfunctions during the flight. The density altitude was calculated to be about 6,200 feet.

Probable cause

the pilot's failure to obtain and maintain an adequate airspeed, which resulted in a stall/mush. A factor in the accident was the high density altitude.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX06CA194
Event ID
20060707X00894
Case number
LAX06CA194
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: 89d3572243622f575c081e7b50f0f35b3d9dce2342891065b81016ac7c6c3685; retrieved 2026-09-22T04:49:56.348Z.