FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24FA215 · Cessna 182

28 Jun 2024 · Big Creek, ID, United States

Cessna 182 · Accident: collision during takeoff/landing during initial climb

From Smiley Creek Airport (U87) to an unrecorded destination

Report a problem

Event

NTSB case
WPR24FA215
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
1 · 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
N6210A
Operator
Unknown
Onboard fatalities
Unknown
Route
From Smiley Creek Airport (U87), Smiley Creek, IDTo not recorded
Aircraft age
About 68 years (built 1956)
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
Defining eventThe 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
Collision during takeoff/landing
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
Tree(s)
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

  • Aircraft › Aircraft handling/service
  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

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

NTSB narrative

After reviewing a standard operating procedures (SOP) guide for the airport, which strongly recommended an airport checkout, the pilot and the pilot-rated passenger entered the traffic pattern to land at the back country turf landing strip in the slightly over-gross-weight airplane with a slight tailwind. While on the downwind leg, the pilot used a higher-than-recommended traffic pattern altitude and turned to the base leg earlier than published recommendations. The pilot then maneuvered to make the runway while the concerned pilot-rated passenger asked him if he was going to go around. The pilot continued the approach and, after flying over most of the runway, initiated a go-around at an altitude below the recommended abort altitude specified in the SOP; at the lowest point of its approach, the airplane was about 10 to 30 ft above ground level (agl). According to the SOP, “Abort altitudes may vary for every type of aircraft and situation. 200-300 ft AFE [agl] is a good altitude for most aircraft.” During the go-around, the pilot applied power and maneuvered to avoid obstacles; however, the airplane impacted trees and terrain about 1,500 ft southeast of the departure end of the runway. During the go-around, the pilot varied the flap position in a method not detailed in the owner’s manual; benefits of this technique could not be determined by the available data. Engine data monitor (EDM) data indicated that during the go-around, the engine’s speed did not increase to the maximum rpm, despite the maximum manifold pressure being used, which suggests the adjustable propeller may have remained set at a higher-than-desired pitch angle. The impact with the trees substantially damaged the wings, empennage, and fuselage. Examination revealed no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. Postmortem toxicology testing of the pilot detected medications that can cause sedation and psychomotor impairment; however, whether the pilot was impaired at the time of the accident could not be determined from toxicological evidence alone. The pilot-rated passenger reported that the pilot’s skills and decision making seemed fully intact.

Probable cause

The pilot’s delayed decision to go around after descending below the recommended abort altitude with a slight tailwind and an over-gross-weight airplane, which resulted in impact with trees and terrain. Contributing to the accident was the pilot’s failure to follow the published guidance for airport operations.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24FA215
Event ID
20240629194573
Case number
WPR24FA215
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: a5ba11fabc585acd8a57e6fcbf1c03c3f25eb09c59fbcf8053382ac5e75c93d4; retrieved 2026-09-15T08:19:48.504Z.