FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA07CA198 · Cessna 182B

15 Jul 2007 · Leadore, ID, United States

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

From Leadore Airport (U00) to Idaho Falls Regional Airport (IDA)

Report a problem

Event

NTSB case
SEA07CA198
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 182B

Aircraft type
Cessna 182
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
N2625G
Operator
Unknown
Onboard fatalities
Unknown
Route
From Leadore Airport (U00), Leadore, IDTo Idaho Falls Regional Airport (IDA), Idaho Falls, ID
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
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
  • Pilot in command › Compensation for wind conditions, inadequate

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 the airplane was about 20 feet above ground level during the initial takeoff climb when a "heavy wind started." The airplane was pushed right about 30 to 40 feet, and then the right wing "went straight up." The pilot said that he took corrective action and leveled the wings. At that point, the airplane "quit flying," struck the ground, and nosed over coming to rest on its back. According to the pilot, the winds were calm when he started the takeoff, and "black clouds came in over the west mountain ridge" after he started the takeoff roll.

Probable cause

The pilot's inadequate compensation for the gusty wind conditions and his failure to maintain aircraft control, which resulted in a loss of control and collision with terrain during the takeoff initial climb. A contributing factor was the gusty wind condition.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA07CA198
Event ID
20070808X01141
Case number
SEA07CA198
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: 6e10e9694efdf265819efe383d0802242d114ab79bd5da5e5e13214dbcda938e; retrieved 2026-09-22T03:39:28.462Z.