SEA07CA122 · Piper PA-22
Piper PA-22 · Accident: in flight collision with terrain/water during initial climb
From Chiloquin State Airport (2S7) to Chiloquin State Airport (2S7)
Event
- NTSB case
- SEA07CA122
- 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
Piper PA-22
- Aircraft type
- Piper PA-22
- 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
- N1394C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chiloquin State Airport (2S7), Chiloquin, ORTo Chiloquin State Airport (2S7), Chiloquin, OR
- 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
- In flight collision with terrain/water
- 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
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot reported that shortly after takeoff from runway 35, "the plane settled and would not climb. I believe we were in a downdraft. Thinking we could not clear rising terrain ahead, I turned into the wind." The pilot stated that after turning into the wind the airplane climbed better, but he still felt as if the airplane was in a downdraft. After maneuvering the airplane, the pilot acknowledged that the airplane was going to contact the ground and pulled the yoke full aft "to land uphill." The airplane contacted the ground, encountered heavy brush, and nosed-over resulting in substantial damage. The pilot did not report any pre-accident mechanical anomalies. The pilot reported that the airplane's gross weight at takeoff was 1,989 pounds. He reported that the airplane's maximum gross takeoff weight was 2,000 pounds. The winds were from 320 degrees magnetic at 10 knots, gusting to 15 knots. The temperature was 50 degrees F and the airport elevation was 4,217 feet above mean sea level (msl).
Probable cause
The pilot's failure to maintain aircraft control during takeoff and initial climb. High vegetation was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA07CA122
- Event ID
- 20070616X00746
- Case number
- SEA07CA122
- 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: 9d58c43b5abee6d0334d6da6dc73ef6818494f7369cedc898579e603d4da2cc5; retrieved 2026-09-21T08:49:13.510Z.