WPR11CA397 · Cessna 170B
Cessna 170B · Accident: controlled flight into terrain/object (CFIT) on approach
From Albany Municipal Airport (S12) to Jefferson, OR (private airstrip)
Event
- NTSB case
- WPR11CA397
- 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 170B
- Aircraft type
- Cessna 170
- 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
- N2789D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Albany Municipal Airport (S12), Albany, ORTo Jefferson, OR (private airstrip)
- 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
- Approach · VFR pattern final
- 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
- Controlled flight into terrain/object (CFIT)
- 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
- Wire
- 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
- Environmental issues › Physical environment
- Personnel issues › Psychological
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 landing on a grass field toward the west just prior to sunset. During the final approach, about 30 feet above ground level, he became aware of power transmission lines directly ahead. The airplane struck the lines and descended to the ground. The airplane sustained substantial damage during the accident sequence, and the pilot and passenger sustained minor injuries. According to the United States Naval Observatory Astronomical Applications Department, the altitude and azimuth of the sun at 1940 in the closest town were 5 degrees and 283.4 degrees, respectively. The pilot reported no preimpact mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation. He stated that this was the first time he had flown to this location, and that he did not overfly the field or perform a thorough review of the area prior to attempting the landing.
Probable cause
The pilot's failure to maintain clearance from power transmission lines during the landing approach into the sun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR11CA397
- Event ID
- 20110822X05515
- Case number
- WPR11CA397
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2011-08-19.
- API snapshot SHA-256: 3d3fd9347e0a823ea54247e7db9fcf24043f8fec0fce959890eb89ae85feaf63; retrieved 2026-09-15T16:38:27.554Z.