FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA07CA186 · Cessna 182

22 Jun 2007 · Bear Lake, ID, United States

Cessna 182 · Accident: airframe, component or system failure during takeoff

From Logan-Cache Airport (KLGU) to Bear Lake County Airport (1U7)

Report a problem

Event

NTSB case
SEA07CA186
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 182

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
N3570B
Operator
Paul R. Thatcher · private individual
Onboard fatalities
Unknown
Route
From Logan-Cache Airport (KLGU), Logan, UTTo Bear Lake County Airport (1U7), Bear Lake, 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
Takeoff · roll/run
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
Airframe, component or system failure
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

  • Miscellaneous, bolt/nut/fastener/clamp/spring › Separation
  • Pilot in command › Nosewheel steering, not possible

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Unbeknownst to the pilot, during the takeoff roll, the bolt that secured the nosewheel steering torque arm to the nosewheel strut separated from the aircraft. When the pilot landed at his planned destination, he had no nosewheel steering, and during his attempt to maintain directional control, the aircraft skidded sideways on the runway, resulting in substantial damage to the airframe. The bolt was later found laying on the runway from which he departed. The castellated nut and cotter pin that normally secure the bolt in place where not located. During his preflight, the pilot had failed to notice that the bolt was no longer properly secured in place.

Probable cause

The separation of the bolt that holds the nosewheel steering torque arm to the nose wheel strut during the takeoff roll, resulting in no nosewheel steering being available during the landing roll at the pilot's destination. Factors include the pilot's failure to notice during his preflight that the bolt was no longer properly secured in place.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA07CA186
Event ID
20070723X00992
Case number
SEA07CA186
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: 709d2d3dd0d7de326d049d7e87622e5ee698f083689aa7db69654e864ab06e4b; retrieved 2026-09-22T03:44:06.728Z.