17 Jan 2017: PIPER PA-32 260 — Van Air

17 Jan 2017: PIPER PA-32 260 (N4261T) — Van Air

No fatalities • Pilot Point, AK, United States

Probable cause

The pilot's continued flight into known icing conditions, which resulted in structural icing and a forced landing on icy, snow-covered terrain.

— NTSB Determination

Accident narrative

On January 16, 2017, about 1520 Alaska standard time, a Piper PA-32-260 airplane, N4261T, was substantially damaged during a forced landing to snow-covered terrain about 5 miles south of the Pilot Point Airport (PNP), Pilot Point, Alaska. The airline transport pilot and sole passenger sustained serious injuries. The airplane was registered to a private individual and operated by Van Air Inc., Dillingham, Alaska, as a Title 14 Code of Federal Regulations Part 135 commercial on-demand passenger flight. A visual flight rules (VFR) flight plan was filed and activated. Day instrument meteorological conditions prevailed at the time of the accident. The flight departed PNP about 1505 destined for Port Heiden Airport (PTH), Port Heiden, Alaska.

The pilot stated that the chartered passenger flight originated from Dillingham Airport (DLG), Dillingham, about 1350 destined for PTH with one passenger. While en route over the Pilot Point area, at an altitude of 800 feet and about 48 miles from the destination, the windshield started accumulating trace ice. The pilot landed the airplane at PNP and called the PTH village agent who reported the destination weather to be good with visibility 10 miles, clouds at 3,000 feet scatted, and no reported icing. The pilot asked the passenger if she knew anyone in Pilot Point that she could stay with that night, and she responded no and stated that she preferred to return to Dillingham if the airplane could not make it to the destination. The pilot decided to take off and continue the flight toward the intended destination to "take a look," and if the weather deteriorated, he would return to Dillingham.

According to the pilot, the airplane departed PNP and continued southwest at 800 feet. About eight miles south of PNP, the wind screen started to accumulate ice, so he maneuvered the airplane back toward the north as planned. The passenger stated that after departing PNP, the visibility deteriorated, and the airplane was in clouds or fog after it turned around, and the engine did not sound right. The pilot stated that the aircraft began accumulating light structural ice and the engine started "running rough." He turned on the carburetor heat and engine performance was restored briefly. About 6 miles south of PNP at 500 feet, severe icing and visibility below 1 mile was encountered. The flight controls became sluggish, all the windows started icing over rapidly, and the engine surged with strong propeller vibrations. The airplane would not maintain altitude and descended through 400 feet. The pilot performed a forced landing on an easterly heading near the King Salmon River and Ugashik River confluence. During the landing sequence, the right main landing gear and the nose landing gear sheared off due to impact with ground ice. The fuselage, right wing, and right horizontal stabilizer sustained substantial damage. (Refer to figure 1.) The pilot and passenger sustained serious injuries during the impact and successfully egressed the airplane. Together they operated the Emergency Locator Transmitter, a mobile marine radio and the strobe light to effect rescue. The passenger, using her cell phone, called the Federal Aviation Administration Flight's Service Station in Dillingham to report the accident. A U.S. Coast Guard MH-60 helicopter extracted the survivors from the remote location about 1830.

The closest weather reporting facility is PNP, about 5 miles north of the accident site. At 1521, an aviation special weather report (SPECI) stated in part: wind from 140 degrees at 5 knots; sky condition, overcast at 1,600 feet; visibility 1 ¾ statute miles in light snow; temperature 7°F; dewpoint 1°F; barometric pressure 29.23 inches mercury.

A review of the Alaska Aviation Weather Unit graphic forecast charts indicated marginal VFR conditions along the route of flight with no significant icing or turbulence forecast. There were no published pilot reports (PIREPs) of icing conditions in the area. Also, the pilot stated that he obtained weather information from National Weather Service online services and determined no significant weather was forecast.

The pilot stated that there were no preimpact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

Figure 1. N4261T PA-32-260 wreckage at the accident scene.

Contributing factors

  • cause Pilot
  • cause Decision related to condition
  • cause Effect on operation
  • Contributed to outcome

Conditions

Weather
IMC, wind 140/05kt, vis 1.75sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.