Cessna 210L accident near Aurora, Oregon, February 18, 2010
On February 18, 2010 at about 5:30 pm local time, a Cessna 210L, registered N777FW, was substantially damaged in an accident during landing (landing roll) near Aurora, Oregon (Aurora State airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 6 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The failure of the landing gear to properly function for undetermined reasons, resulting in the right main landing gear collapsing during landing. Contributing to the accident was the pilot's failure to follow the emergency gear extension procedure.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 18, 2010 · about 5:30 pm local time · cases in 2010
- Place
- Aurora, Oregon · Aurora State · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 6 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 210L · all 210Ls on the register
- Registration
- N777FW · registry record · serial 21060167
- 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, after departing for a local flight, he attempted to retract the landing gear but the landing gear did not retract. He verified the position by looking out of the window and noted that the landing gear appeared to be in the down-and-locked position. The green landing gear position light was not illuminated. Because he thought that the landing gear was in the down-and-locked position, the pilot decided not to use the manual gear extension procedure. During the landing, the right main landing gear collapsed. Postaccident examination and testing of the landing gear system showed that it operated normally and no mechanical anomalies were identified. The underlying cause of the intermittent operation of the landing gear system was not determined. Testing of the manual gear extension system showed that it functioned normally. Had the pilot used the system, he would have received a gear down-and-locked indication and landed normally.
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
- Sys/Comp malf/fail (non-power) during initial climb
- Landing gear collapse during landing (landing roll) defining event
The NTSB's findings
- cause Aircraft › Aircraft systems › Landing gear system › Gear extension and retract sys › Malfunction other cases naming the landing gear
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
- factor Personnel issues › Action/decision › Action › Lack of action › Pilot
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land; instrument: airplane
- Flight time: 611 hours in all; 266 in this make and model; 5 in the last 90 days; 575 as pilot in command
- Last flight review: April 14, 2009
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 13,762 hours
- Last inspection: annual inspection, April 8, 2009; 62 hours since
- Maximum gross weight: 3,800 lb
- Seats: 6
- Landing gear: retractable
- Engine: Teledyne Continental Motors IO-520 (piston); 0 hours total
The flight
- Departed from: UAO Aurora OR at 5:25 pm
- Destination: UAO Aurora OR
- Flight plan: not recorded
- Runway 35, 5,004 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 070° at 10 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 55°F (13°C), dew point 34°F (1°C)
- Altimeter: 30.04 inHg
- Observation at 5:53 pm from UAO
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 5 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on September 28, 2010. 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 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 17 pages | View Download |
| 2 | FAA Record of Conversation | PDF, 1 page | View Download |
| 3 | Photo 1. Airplane (Provided by Airport) | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N777FW on the register today · the tail number may have moved to another aircraft since
- Cessna 210 Centurion 1,523 registered today · the model family and its accident history
- Cessna 72,672 aircraft on the register
- Engine: Teledyne Continental Motors IO-520 9,482 aircraft carry this series today · as the NTSB recorded it
- Aurora State Airport · nearest airport
- 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/WPR10LA140.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.