FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13FA336 · Robinson R66

27 Jul 2013 · Noxen, PA, United States

Robinson R66 · Accident: VFR encounter with IMC en route

From Tri Cities Airport (CZG) to Jake Arner Memorial Airport (22N)

Report a problem

Event

NTSB case
ERA13FA336
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
5 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Robinson R66

Aircraft type
Robinson R66
Category
Helicopter
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N646AG
Operator
David E. Jenny · private individual
Onboard fatalities
Unknown
Route
From Tri Cities Airport (CZG), Endicott, NYTo Jake Arner Memorial Airport (22N), Lehighton, PA
Aircraft age
Built the same year (2013)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
VFR encounter with IMC
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight departed under visual flight rules (VFR) and then obtained VFR flight following before proceeding in a southeasterly direction. About 28 minutes after takeoff, while flying about 3,000 feet mean sea level over a sparsely populated and heavily wooded area with few ground reference lights, the flight likely encountered light rain. The pilot flew south of a wind turbine, initiated an approximate 180-degree left turn with 300 feet altitude loss, then began following a dirt road associated with the wind turbines. After completion of the turn he advised the controller, "...we're inadvertent IMC [instrument meteorological conditions], reversing..." and asked for a heading to the nearest airport. The controller asked the pilot if he wanted a vector to the nearest airport and also if the flight was in IMC, but there was no reply. The controller provided a heading for a vector to a nearby airport but the pilot did not respond. The flight continued in the same orientation following the course reversal, flying past another wind turbine before turning right; the controller again advised the pilot of the direction to the nearest airport. The pilot immediately responded that he was, "...having trouble maintaining control here." The controller informed the pilot that the nearest airport was heading 068 degrees and 8 miles away, and the recorded radar data indicates the pilot flew a north-northeasterly heading with changes in altitude noted. The comments from the pilot followed by the maneuvering (changes in altitude and heading) were consistent with the known effects of spatial disorientation. Radio and radar contact were lost; the helicopter descended on an east-northeasterly heading into trees and terrain in a heavily wooded area away from any nearby wind turbines.

Postaccident examination of the helicopter revealed extensive impact damage, although there was no evidence of a preimpact failure with the flight controls, drive line, or structure. The engine was found to operate normally and data downloaded from the engine monitoring unit indicates no evidence of preimpact failure or malfunction.

While there was no record of an official preflight weather briefing before departure, a text message from the non-instrument rated pilot to his brother approximately 1 hour before departure stating, "...Waiting out weather to fly back to [Ocean City, MD] tonight" indicates that to some extent he was aware of the weather. Had the pilot obtained an official preflight weather briefing for the intended VFR flight, the briefing specialist likely would have advised him against VFR flight due to IMC (ceiling less than 1,000 feet and visibility less than 3 miles) and mountain obscuration that were forecast to exist in the accident area.

Although the left seat occupant was a student pilot, it is unlikely the pilot-in-command was giving him instruction during the accident flight. While operation of a helicopter with decreased ceiling and visibility can be safely performed, the environmental conditions in the accident site area consisting of a sparsely populated heavily wooded area with few ground reference lights and no illumination from the moon were indicators that VFR flight should not have continued.

Probable cause

The pilot's decision to continue VFR flight into night instrument meteorological conditions, which resulted in spatial disorientation and a loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13FA336
Event ID
20130728X45845
Case number
ERA13FA336
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2013-07-28.
  • API snapshot SHA-256: a131940cb3e60f228c723b6419a72a95007426569a747cd688eb6dda367a3292; retrieved 2026-09-14T16:01:27.167Z.