Piper PA-32-300 accident near Nunapitchuk, Alaska, April 10, 2009
On April 10, 2009 at about 6:45 pm local time, a Piper PA-32-300, registered N43551, was substantially damaged in an accident during approach (VFR pattern final) near Nunapitchuk, Alaska (Nunapitchuk airport). 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 maintain sufficient airspeed to avoid a stall during the landing approach.
Source: NTSB aviation accident database, copy made October 12, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 10, 2009 · about 6:45 pm local time · cases in 2009
- Place
- Nunapitchuk, Alaska · Nunapitchuk · 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
- Piper PA-32-300 · all PA-32-300s on the register
- Registration
- N43551 · no longer on the register · serial 32-7440133
- Damage
- Substantial damage
- Flight
- Flight · charter and air-taxi rules (Part 135)
The NTSB's narrative final · quoted from the NTSB record
The solo commercial pilot was en route to a rural airport on a Title 14, CFR Part 135 air taxi flight with a load of cargo. During an interview with the NTSB investigator-in-charge on April 10, the pilot stated that the flight was without incident until he began the approach to land. He indicated he had difficulty finding the runway in reduced visibility due to blowing snow. He stated he prematurely slowed the airplane in preparation for landing, as he thought he was closer to the runway than he was. He said that due to his low altitude and the poor visibility, he overshot his turn from left base to final, and while attempting to correct and realign the airplane with the runway, the stall warning horn came on, and the airplane stalled, striking the left wing on terrain west of the runway. The pilot stated that there were no preimpact mechanical problems with the airplane, and that he should have paid more attention to his altitude and airspeed.
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
- Aerodynamic stall/spin during approach (VFR pattern final)
- Loss of control in flight during approach (VFR pattern final) defining event
- Collision with terrain or object (not controlled flight into terrain) during approach (VFR pattern final)
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Snow › Contributed to outcome
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land; instrument: airplane
- Flight time: 3,178 hours in all; 199 in the last 90 days; 1,608 as pilot in command
- Last flight review: October 28, 2008
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 9,804 hours
- Last inspection: 100-hour inspection, February 21, 2009; 45 hours since
- Maximum gross weight: 3,400 lb
- Seats: 2
- Landing gear: fixed
- Engine: Lycoming TIO-540 SER (piston); 0 hours total
- Operator: J P Air Service LLC
The flight
- Departed from: PABE Bethel AK at 1:30 pm
- Destination: 16A Nunapitchuk AK
- Flight plan: not recorded
- Runway 18, 2,420 ft by 70 ft
Weather at the time
- Light: daylight
- Wind: from 010° at 12 knots
- Visibility: 3 statute miles
- Sky: not recorded; not recorded
- Temperature: 32°F (0°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
1 document, released by the NTSB on September 9, 2009. 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, 11 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N43551 the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N43551: not on the register today · the record of its deregistration
- Piper PA-32 Cherokee Six, Lance and Saratoga 3,916 registered today · the model family and its accident history
- Piper 44,848 aircraft on the register
- Engine: Lycoming TIO-540 SER 5,073 aircraft carry this series today · as the NTSB recorded it
- Nunapitchuk Airport · nearest airport
- Bethel Airport · departed from
- Accidents and incidents in Alaska 5,930 since 1982 · 824 in the last ten years
- Alaska 9,146 aircraft registered
- Other NTSB records under N43551 2 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/ANC09LA030.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.