SEA02LA042 · Cessna 172
Cessna 172 · Accident: in flight collision with object while maneuvering
From Yanji Chaoyangchuan Airport (YNJ) to Chilliwack Airport (YCW)
Event
- NTSB case
- SEA02LA042
- 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
- Not recorded
Cessna 172
- Aircraft type
- Cessna 172
- 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
- C-FISS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Yanji Chaoyangchuan Airport (YNJ), LANGLEY, BCTo Chilliwack Airport (YCW), CHILLIWAK, BC
- 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
- Maneuvering
- 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 object
- 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
- Pilot in command › Altitude/clearance, 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 was following the Skagit River eastbound approximately 1500-1800 feet above sea level when he observed rain showers ahead and he decided to execute a course reversal. He initiated a left turn at 75 miles per hour utilizing two "notches" (20 degrees) of flaps and noted a sink rate. He then applied full power and raised the flaps to one "notch" (10 degrees) during which the sink rate continued. The pilot reported that it "felt like the aircraft was getting sucked down." As the aircraft continued in its left turn towards the rising, tree covered hillside, the pilot executed a controlled crash into the trees and terrain. A topographic chart of the vicinity of the accident showed that the terrain gradient was considerably shallower to the south, and that the left turn initiated by the pilot placed the aircraft flying towards higher gradient terrain. The pilot reported that he had been using carburetor heat throughout the flight and that the aircraft's engine had been performing as expected.
Probable cause
The pilot's failure to maintain adequate clearance/altitude while reversing course and turning towards rising, tree covered terrain in downdraft conditions. Contributing factors were trees, rising terrain, downdrafts and the pilot's in-flight decision to turn towards rather than away from steeper terrain during his course reversal.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA02LA042
- Event ID
- 20020228X00290
- Case number
- SEA02LA042
- 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: c7d1d2ab3f7184bb442fb1660d061e01d66c8248c1bbdc0e71aecd72fff8cc68; retrieved 2026-09-22T11:06:58.313Z.