16 Sep 2016: HELIO H 295 — Wright Air Service

16 Sep 2016: HELIO H 295 (N6464V) — Wright Air Service

No fatalities • Fairbanks, AK, United States

Probable cause

Excessive side loads imposed on the tailwheel A-frame during the takeoff roll, which resulted in a separation of the tailwheel and the subsequent loss of directional control.

— NTSB Determination

Accident narrative

On September 16, 2016, about 0820 Alaska daylight time, a tundra tire-equipped Helio Courier H-295 airplane, N6464V, sustained substantial damage following a loss of control and subsequent runway excursion during takeoff from a remote, unimproved airstrip near Fairbanks, Alaska. The airplane was being operated by Wright Air Service, Fairbanks, Alaska, as a visual flight rules (VFR) on-demand commercial flight under the provisions of 14 Code of Federal Regulations (CFR) Part 135. The certificated airline transport pilot and one passenger were not injured. Visual meteorological conditions prevailed, and a VFR flight plan had been filed.

During an interview with the National Transportation Safety Board (NTSB) investigator-in-charge on September 20, the pilot stated that everything seemed normal as he initiated the takeoff. About 300 feet into the takeoff roll, the airplane veered sharply to the left, exited the airstrip and impacted brush and trees, resulting in substantial damage to the fuselage and left horizontal stabilator.

The initial examination of the airplane, reported by the pilot, revealed that the tailwheel separated from its attach point and folded underneath the empennage. A trench was visible in the airstrip's surface that began about 300 feet from the point where the takeoff roll was initiated and continued to where the airplane impacted the brush and trees.

The tailwheel A-frame consisted of two arms extending forward of a flanged downtube, with a brace cross tube present between the two forward facing arms. The tailwheel A-frame was attached to the airframe at the forward ends of the arms, and to a shock absorber on the aft side of the down tube. Corner braces reinforced the attachments between the arms and the downtube. The corner brace between the left arm and the downtube was buckled and cracked, and the left arm was fractured where it was welded to the downtube. The tailwheel A-frame assembly was sent to the NTSB's Materials Laboratory in Washington D.C. for examination.

An NTSB Senior Materials Engineer reported that visual and magnified optical examinations of the fractures in the left arm revealed a matte gray fracture on slant planes consistent with a ductile overstress fracture. However, a portion of the fracture surface had a fracture in a plane perpendicular to the surface across most of the fracture with small shear lips present. Two areas had no shear lips at the surface and were oxidized with smooth curving boundaries, consistent with fatigue. The right arm had a crack that was opened in the laboratory. Examination of the fracture revealed that a portion of the fracture surface at the upper side of the right arm was on a plane perpendicular to the surface and was oxidized with curving black arrest lines, features consistent with fatigue. The remainder of the fracture surface had matte gray features on slant planes across the thickness of the arm wall. The fatigue regions in the left and right arms were up to 0.016 inch deep and 0.066 inch deep, respectively. The fracture surfaces where the brace tube between the arms had separated from the right arm were examined. The fracture features had matte gray features on slant planes consistent with ductile overstress fracture. In addition, fracture features where the shock absorber attachment ear fractured had features consistent with ductile overstress fracture. (Refer to the Materials Laboratory Factual Report in the public docket for further fracture information)

The closest weather reporting facility was Fairbanks International Airport, Fairbanks, Alaska, about 42 miles south of the accident site. At 0753, an aviation routine weather report (METAR) from Fairbanks Airport, was reporting in part: wind from 050° at 4 knots; visibility, 10 statute miles; sky condition, broken clouds 5,500 feet, broken clouds 7,500 feet, broken clouds 15,000 feet; temperature, 39° F; dew point 37° F; altimeter, 29.36 inHG.

Contributing factors

  • cause Nose/tail landing gear — Failure
  • cause Attain/maintain not possible
  • Contributed to outcome

Conditions

Weather
VMC, wind 050/04kt, vis 10sm

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.