Fairchild SA227-AC accident near Seattle, Washington, March 11, 2011
On March 11, 2011 at about 2:41 am local time, a Fairchild SA227-AC, registered N671AV, was substantially damaged in an accident during landing (flare/touchdown) near Seattle, Washington (Boeing Field King County Int.). It was flown under charter and air-taxi rules (Part 135). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to extend the landing gear, which resulted in a gear-up landing.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 11, 2011 · about 2:41 am local time · cases in 2011
- Place
- Seattle, Washington · Boeing Field King County Int. · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Fairchild SA227-AC · all SA227-ACs on the register
- Registration
- N671AV · registry record · serial AC671
- Damage
- Substantial damage
- Flight
- Flight · charter and air-taxi rules (Part 135)
The NTSB's narrative final · quoted from the NTSB record
The pilot reported that following two attempts to land in crosswind conditions, he was cleared to land and was instructed by the air traffic control tower controller to follow another airplane on final approach. For spacing considerations, the controller instructed the pilot to conduct "S" turns behind the traffic landing ahead of him. As the airplane descended to an altitude of about 200 feet above ground level, the controller instructed the pilot to go around and maintain altitude. The pilot executed a go-around procedure, which included retracting the landing gear and reducing the flap setting to one-half flaps. Shortly after, the pilot was issued a clearance to land. The pilot proceeded with the landing clearance and subsequently landed with the gear in the retracted position, which resulted in structural damage to the airframe. Postaccident examination of the airplane revealed no mechanical anomalies or failures with the landing gear or landing gear warning system.
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
- Landing gear not configured during landing (flare/touchdown) defining event
- Runway excursion during landing (flare/touchdown)
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Forgotten action/omission › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Configuration › Incorrect use/operation
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
- Flight time: 2,432 hours in all; 78 in this make and model; 130 in the last 90 days; 55 in the last 30 days; 2,294 as pilot in command
- Last flight review: February 15, 2011
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 21,847 hours
- Last inspection: approved inspection programme, February 21, 2011; 88 hours since
- Maximum gross weight: 14,500 lb
- Seats: 12
- Landing gear: retractable
- Engine 1: Airesearch TPE331 SERIES (turboprop); 0 hours total
- Engine 2: Airesearch TPE331 SERIES (turboprop); 0 hours total
- Operator: Ameriflight INC
The flight
- Departed from: Lewiston ID at 1:15 am
- Destination: BFI Seattle WA
- Flight plan: IFR
- Runway 13R, 10,000 ft by 100 ft
Weather at the time
- Light: night
- Wind: from 200° at 16 knots, gusting 28
- Visibility: 10 statute miles
- Sky: broken clouds at 12,000 ft; scat at 8,500 ft
- Temperature: 45°F (7°C), dew point 37°F (3°C)
- Altimeter: 29.86 inHg
- Observation at 2:53 am from BFI
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
3 documents, released by the NTSB on October 28, 2011. 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, 9 pages | View Download |
| 2 | Pilot Statement | PDF, 1 page | View Download |
| 3 | Record of Conversation - Federal Aviation Administration Inspector | 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
- N671AV on the register today · the tail number may have moved to another aircraft since
- Fairchild SA227 86 registered today · the model family and its accident history
- Fairchild 616 aircraft on the register
- Engine: Airesearch TPE331 SERIES 491 aircraft carry this series today · as the NTSB recorded it
- Engine: Airesearch TPE331 SERIES 491 aircraft carry this series today · as the NTSB recorded it
- Boeing Fld/King County International · nearest airport
- Accidents and incidents in Washington 2,713 since 1982 · 361 in the last ten years
- Washington 10,663 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR11FA159.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.
