Cessna 172 accident near Mckenzie Bridge, Oregon, August 28, 2019
On August 28, 2019 at about 1:35 am local time, a 1958 Cessna 172, registered N4108F, was destroyed in an accident during takeoff near Mckenzie Bridge, Oregon (Mc Kenzie Bridge State airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's delayed climb and misjudgment of the airplane’s performance and the runway distance needed to clear obstacles at the end of the runway, which resulted in a collision with trees and subsequent impact with terrain. Contributing to the accident was the pilot's insufficient experience landing and taking off at mountain airports.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 28, 2019 · about 1:35 am local time · cases in 2019
- Place
- Mckenzie Bridge, Oregon · Mc Kenzie Bridge State · cases near this airport · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172 Undesignat, built 1958 · all 172s on the register
- Registration
- N4108F · no longer on the register · serial 46008
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
After flying over mountainous terrain, the pilot attempted an approach into an airport with a 2,600-ft-long grass runway bordered by tall trees. Witnesses near the center of the runway described the airplane flying east over the runway about 5 ft above ground level when it came into their view. One witness stated that he could not hear any noise as the airplane came into view but that its wings rocked; he said he heard the engine power increasing and that the airplane may have started to climb when it reached his center of vision. A second witness stated that she heard the engine running and that the airplane began a slow climb and then disappeared from her view behind trees at a slightly higher altitude. About 15 minutes later, they saw smoke coming from the accident site. Impact signatures indicated that the airplane contacted treetops during the climbout; it then impacted the ground and came to rest inverted about 615 ft east of the departure end of the runway. The witness statements support that the airplane was developing power when it began the climb. The propeller signatures were inconsistent with the engine producing power at the time of the impact; however, it is unknown if the pilot reduced power before impact. Rotational continuity of the engine and valve train could not be achieved because the engine crankcase and accessories were damaged by postcrash fire and the oil sump was destroyed. Although the crankshaft, camshaft, connecting rods, and piston were mostly damaged by postcrash fire, an examination of these components and the interior engine case revealed no indications of catastrophic engine failure. Calculations based on takeoff and climb performance charts from the pilot's operating handbook showed that the airplane required a total takeoff distance of about 1,330 ft to clear a 50-ft obstacle at the end of the runway. However, the chart did not account for the 134 ft of rising terrain and 120-ft-tall trees at the end of the runway or the ambient temperature of about 98°F. The calculated density altitude on the day of the accident was 4,481 ft, which would have reduced the airplane's climb performance. Given these conditions, it is unlikely that the airplane was capable of clearing the rising terrain and tall trees at the end of the runway on the day of the accident. Review of the pilot's logbook showed that he had not performed landings or takeoffs at mountain airports. Thus, he had insufficient experience to attempt a landing or takeoff at a short mountain airport runway bordered by trees on a day with a density altitude over 2,800 ft higher than the airport elevation. While it is unknown if the pilot had intended to perform a full-stop landing, a touch-and-go maneuver, or overfly the runway at a low altitude, he had selected a runway that was not recommended for takeoffs but was recommended for landing. The pilot likely misjudged the runway length needed and the airplane's performance when he chose to begin a climb about midfield in high density altitude conditions with rising terrain and 120-ft obstacles at the end of the runway.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Miscellaneous/other during takeoff
- Collision during takeoff/land during takeoff defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Personnel issues › Action/decision › Action › Delayed action › Pilot
- cause Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Contributed to outcome
- cause Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Contributed to outcome
- factor Personnel issues › Experience/knowledge › Experience/qualifications › Total experience › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 69 hours in all; 69 in this make and model; 30 in the last 90 days; 7.5 in the last 30 days; 40 as pilot in command
- Last flight review: July 29, 2019
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 4,836.8 hours
- Last inspection: 100-hour inspection, August 25, 2019; 4 hours since
- Maximum gross weight: 2,299 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental O-300-A (piston); 2,530 hours total
- Fire on the ground
The flight
- Departed from: S30 Lebanon OR
- Destination: S30 Lebanon OR
- Flight plan: none
- Runway 06, 2,600 ft by 90 ft
Weather at the time
- Light: daylight
- Wind: from 330° at 10 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 99°F (37°C), dew point 46°F (8°C)
- Altimeter: 29.73 inHg
- Observation at 1:54 am, 48 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Photographs from the investigation 7 pictures from the NTSB's docket, as the NTSB released them
Photo 1 – Main Wreckage
Photo 2 – Quartering View of Main Wreckage
Photo 3 – View of Accident Site from Tail
Photo 4 – Engine at Examination Facility
Photo 5 – Engine and Accessory Case
Photo 6 – Wreckage Path Diagram (Figure 1 in Factual Report)
Photo 7 – Terrain Elevations Along Flight Path (Figure 2 in Factual Report)The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
12 documents, released by the NTSB on March 23, 2021. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Weather Reports and Records | PDF, 4 pages · our copy | View Download |
| 2 | FAA Chart Supplement | PDF, 1 page · our copy | View Download |
| 3 | Record of Conversations | PDF, 7 pages · our copy | View Download |
| 4 | NTSB Examination Report | PDF, 19 pages · our copy | View Download |
| 5 | Pilot Logbook | PDF, 17 pages · our copy | View Download |
| 6 | Airplane Flight History | PDF, 1 page · our copy | View Download |
| 7 | Excerpt from Pilot's Operating Handbook | PDF, 4 pages · our copy | View Download |
| 8 | Weight and Balance | PDF, 1 page · our copy | View Download |
| 9 | Fuel Records | PDF, 1 page · our copy | View Download |
| 10 | Statement of Party Representatives to NTSB Investigation | PDF, 2 pages · our copy | View Download |
| 11 | Pilot Toxicology, Federal Aviation Administration | PDF, 2 pages · our copy | View Download |
| 12 | Accident Photographs | PDF, 7 pages · our copy | View Download |
Connections how this case links to the rest of the register
- N4108F: not on the register today · the record of its deregistration
- Cessna 172 Skyhawk 20,691 registered today · the model family and its accident history
- Cessna 72,672 aircraft on the register
- Engine: Continental O-300-A 15 aircraft carry this series today · as the NTSB recorded it
- MC Kenzie Bridge State Airport · nearest airport
- Lebanon State Airport · departed from
- Accidents and incidents in Oregon 1,864 since 1982 · 279 in the last ten years
- Oregon 6,998 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR19FA244.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
