10 Sep 2014: PIPER J3C 65 65 — HEIMOS BERNARD F

10 Sep 2014: PIPER J3C 65 65 (N26105) — HEIMOS BERNARD F

No fatalities • Carrol County, VA, United States

Probable cause

The pilot’s failure to maintain clearance from trees during an emergency landing after encountering deteriorating weather conditions. Contributing to the accident was the pilot’s poor preflight weather planning, which resulted in an inadvertent encounter with instrument meteorological conditions.

— NTSB Determination

Accident narrative

On September 10, 2014, about 1309 eastern daylight time, a Piper J3C-65 Cub, N26105, was substantially damaged during an emergency landing and subsequent in-flight collision with trees and terrain near Carroll County, Virginia. The private pilot was seriously injured. Instrument meteorological conditions prevailed and no flight plan was filed for the flight that originated from Raleigh County Memorial Airport (BKW), Beckley, West Virginia at 1145, and was destined for Smith Reynolds Airport (INT), Winston Salem, North Carolina. The personal flight was conducted under the provisions of 14 Code of Federal Regulations Part 91.

According to a Federal Aviation Administration (FAA) Aviation Safety Inspector, the airplane crashed in a remote, wooded area, about 40 nautical miles (nm) west of BKW, at an elevation of about 2,534 feet. Photographs taken by the Virginia State Police revealed that the airplane was intact with the exception of the right wing which was located in a nearby tree. There were compression wrinkles throughout the wings, fuselage, and empennage. The wings also exhibited aft crush damage on the leading edge.

After recovering from his injuries, the pilot was interviewed by the NTSB investigator-in-charge on October 29, 2014. The pilot reported that he was flying across the United States on a month long cross county flight. After he refueled the airplane at BKW, he departed for INT and followed an interstate highway, as was his custom. About 40 nm from his destination, he encountered some "mist" and descended, but the "the mist got heavier." He then configured the airplane for an emergency landing on the interstate and descended between two tree lines, but the airplane impacted a tree, fell to the ground and came to rest in a nose down attitude. The pilot reported that his attention was focused on the interstate and not on the surrounding obstacles. He also remarked that there were no preimpact mechanical malfunctions or anomalies with the airplane. The pilot stated that his usual method for obtaining weather was by utilizing the Internet application Foreflight, but did not recall if he retrieved weather prior to departing BKW.

According to a Virginia State Trooper, the pilot reported that he made the decision to land the airplane after the weather abruptly changed to fog.

A witness reported that the weather at the time was "foggy and rainy." He stated that he was driving southbound on the interstate and observed the airplane to his left on a southerly heading. The airplane appeared to be cruising above the tree tops and "went straight into the trees".

A review of global positioning system data retrieved from an onboard Garmin GPSMAP 296 revealed that the airplane departed BKW at 1137 and started a climb. The airplane followed the interstate at various altitudes until 1300, when it started a descent from a GPS recorded altitude of about 3,350 feet. At 1308, the airplane leveled off at a GPS altitude of 2,600 feet, and remained in straight and level flight until 1309 when the data ended in the vicinity of the accident site.

A GoPro Hero rugged high definition video recorder was also recovered from the accident site; however, it contained no recorded data.

The pilot held a private pilot certificate with ratings for airplane single engine land and instrument airplane. According to the pilot, he did not possess a current medical certificate and; therefore, was operating the airplane as a sport pilot. At the time of the accident he reported 4,399 total hours of flight experience; 1,423 hours of which were in the accident airplane make and model. The pilot's last instrument proficiency check was during 2005 .

The single-engine, fixed-gear, high wing, reciprocating engine powered airplane, was manufactured in 1939. It was powered by a Continental A75-A 75-horsepower engine, equipped with a Sensenich two-bladed propeller. According to the pilot the airplane was not certified for flight under instrument flight rules.

The National Weather Service (NWS) Boston Area Forecast indicated overcast clouds at 2,500 feet mean sea level (msl) with cloud tops at 7,000 feet, visibility 3-5 statute miles in mist. The weather was forecasted to improve between 1000 and 1300 with scattered clouds at 2,500 feet msl and broken clouds at 4,500 feet. The forecast also included an AIRMET Sierra for mountain obscuration with clouds and mist over the area.

The Washington, D.C. (ZDC) Air Route Traffic Control Center Meteorological Impact Statement (MIS) that was valid from 0729 to 1600 forecasted limited instrument flight rule conditions due to low ceilings, reduced visibility and fog through 1100. The ZDC MIS also described marginal visual flight rule conditions with patchy ceilings and mist across the Washington, D.C. area.

Weather, recorded at Twin County Airport (HLX), elevation 2,694 feet, at 1315, included winds from 180 degrees at 5 knots, visibility 10 statute miles, sky overcast at 700 feet, temperature 19 degrees C, dew point 17 degrees C, an altimeter setting of 30.21 inches Hg. HLX was located 9 nm north of the accident site.

According to a weather report obtained from the Virginia Department of Transportation, the weather recorded about a mile from the accident site, elevation about 2,500 feet, at 1310 included wind calm, air temperature 18 degrees C, dew point 18 degrees C, and visibility 1,030 feet.

Contributing factors

  • cause Awareness of condition
  • factor Pilot
  • factor Use of related info
  • cause Altitude — Not attained/maintained
  • cause Pilot
  • cause Pilot
  • cause Effect on operation
  • cause Effect on operation
  • factor Use of related info

Conditions

Weather
IMC, wind 180/05kt, 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.