Cessna Aircraft CO E162 accident near Eugene, Oregon, September 8, 2013
On September 8, 2013 at about 2:00 am local time, a 2011 Cessna Aircraft CO E162, registered N30265, was substantially damaged in an accident during landing (flare/touchdown) near Eugene, Oregon (Mahlon Sweet Field). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's improper flare that resulted in a bounced landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 8, 2013 · about 2:00 am local time
- Place
- Eugene, Oregon · Mahlon Sweet Field · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna Aircraft CO E162 UNDESIGNAT, built 2011
- Registration
- N30265 · registry record · serial 16200093
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that while on final, the approach was stable, and that on short final he leveled the airplane and flared for landing. The airplane touched down, bounced back into the air, and when it touched down again, it impacted the runway in a nose down attitude. The airplane sustained substantial damage to the firewall. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
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
- Hard landing during landing (flare/touchdown) defining event
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 286 hours in all; 20 in this make and model; 93 in the last 90 days; 36 in the last 30 days
- Last flight review: June 29, 2013
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 783 hours
- Last inspection: condition inspection, July 23, 2013; 81 hours since
- Maximum gross weight: 1,321 lb
- Landing gear: fixed
- Engine: Cont Motor O-200-D1B (piston); 783 hours total
- Operator: Hillsboro Aviation INC
The flight
- Departed from: RBG Roseburg OR at 1:30 am
- Destination: EUG Eugene OR
- Flight plan: VFR
- Runway 34L, 8,009 ft by 150 ft
Weather at the time
- Light: dusk
- Wind: from 010° at 3 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 70°F (21°C), dew point 59°F (15°C)
- Altimeter: 29.95 inHg
- Observation at 2:54 am from KEUG
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Other NTSB records under N30265 the same tail number, which may have belonged to a different aircraft at the time
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.