McCall Aviation Cessna TU206F accident
Cessna TU206F · Accident while maneuvering
From McCall Municipal Airport (MYL) to an unrecorded destination
Event
- NTSB case
- WPR21FA330
- 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
- 2 · 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
- Charter & commuter
- 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 TU206F
- Aircraft type
- Cessna 206
- 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
- N922MA
- Operator
- McCall Aviation
- Onboard fatalities
- Unknown
- Route
- From McCall Municipal Airport (MYL), McCall, IDTo not recorded
- Aircraft age
- About 45 years (built 1976)
- 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 135: Air Taxi & Commuter
- 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
- Maneuvering
- 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
- Unknown or undetermined
- 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 oper/perf/capability
- 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
The pilot departed on a scenic air tour flight with two passengers over an area of mountainous terrain. After surveying the desired location, the pilot chose to fly up a canyon (drainage) to return to the departure airport. The pilot stated that he could not completely recall the events of the accident flight but reported that as the airplane neared the top of the canyon, he realized that the rate of climb was insufficient to clear the terrain ahead, and he initiated a 180° turn. He stated that he remembered extending the wing flaps but did not remember when. After starting the turn, the airplane encountered a downdraft and descended into trees. Data from an onboard GPS device indicated that the airplane entered the canyon at an altitude about 6,000 ft about 4 minutes before the impact. The airplane continued to climb until the final 3 seconds of recorded data. During the last approximate 2 minutes of recorded data, the airplane climbed from an altitude about 7,000 ft to about 8,300 ft. The airplane’s pitch attitude, which had not previously exceeded about 9° nose-up during the flight, exceeded 10° nose-up for much of the final minute of the flight and increased to a maximum of 17° nose-up about 5 seconds before the end of the data. During the final minute of the flight, the speed remained below 80 knots, ultimately decreasing to below 65 knots during the final 15 seconds of recorded data. A performance analysis indicated that, given the airplane’s gross weight and the atmospheric conditions present at the time of the accident, the airplane would have required nearly 2 additional minutes to reach and clear the top of the canyon. Postaccident examination of the wreckage did not reveal any preimpact mechanical anomalies. The wing flaps were found fully extended at the accident site. Full flap extension would have adversely affected the airplane’s climb performance; however, the point at which the flaps were fully extended could not be determined. The pilot had extensive low-level flight experience in military jets; however, he had about 28 total hours and about 3 months of experience in the accident airplane, and the accident flight was his first scenic flight with passengers. Review of weather conditions indicated light wind conditions with no evidence of mountain wave activity. The density altitude in the area of the accident site was near 10,000 ft. The circumstances of the accident are consistent with the pilot’s decision to continue into a canyon that exceeded the climb performance of the airplane, which resulted in impact with terrain during an attempted course reversal.
Probable cause
The pilot’s decision to continue the flight into a canyon that exceeded the performance capabilities of the airplane, which resulted in an impact with trees an terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR21FA330
- Event ID
- 20210829103764
- Case number
- WPR21FA330
- 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 UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: 8cba923106e2e27ff0f5d29df5bf69a3d814b85157d1cfefdedffdb570729c85; retrieved 2026-09-15T07:33:41.239Z.