ERA24FA069 · American Eurocopter Corp AS350B2
US Helicopters American Eurocopter Corp AS350B2 · Accident en route
From Northeast Philadelphia Airport (PNE) to Northeast Philadelphia Airport (PNE)
Event
- NTSB case
- ERA24FA069
- 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
- 2 · all aircraft and ground
- Ground fatalities
- 0
- 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
- Visual Meteorological Cond
American Eurocopter Corp AS350B2
- Aircraft type
- Eurocopter AS350
- 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
- N606HD
- Operator
- US Helicopters
- Onboard fatalities
- Unknown
- Route
- From Northeast Philadelphia Airport (PNE), Philadelphia, PATo Northeast Philadelphia Airport (PNE), Philadelphia, PA
- Aircraft age
- About 10 years (built 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
- Unknown or undetermined
- 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
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter accident occurred during an electronic news gathering (ENG) flight in night visual meteorological conditions. Weather and visibility at the time were good, and though the helicopter had been operating at or near the freezing level, no clouds or precipitation existed along its flightpath. Other air traffic did not appear to be a factor. The pilot and non-pilot videographer departed about 41 minutes before the accident on their third flight of the day. The non-pilot videographer was seated in the back of the helicopter, without access to the flight controls. They arrived at the scene of the assignment about 20 minutes after departing, collected video for about 10 minutes, and then began heading back to base. Up to this point, there were no anomalies with the flight. About 3 minutes before the accident, the helicopter drifted right of its established flight track and passed through its outbound course. Within 1 minute, the helicopter began to descend from an altitude of about 1000 ft mean sea level (msl). The gradual descent continued for about 2 minutes, with the ground speed gradually increasing. The helicopter then impacted terrain and a postimpact fire ensued. Examination of the wreckage did not reveal any evidence of a preimpact failure or malfunction of the helicopter, engine, or its systems that would have precluded normal operation. Examination of the wreckage also did not reveal any evidence of a bird strike. The flight profile, though, was consistent with the pilot becoming incapacitated or falling asleep. The pilot had a history of prediabetes, and toxicological evidence indicated he had used the blood-sugar-controlling medication metformin. His negative urine and vitreous glucose results indicated that he was unlikely to have been experiencing markedly elevated blood sugar at the time of the crash. The glucose results neither excluded nor supported a hypothesis of low blood sugar related to diabetes/prediabetes medication use; however, metformin use is not likely to result in symptomatic low blood sugar. Thus, there is no specific evidence that the pilot’s blood sugar was a factor in the accident. The pilot also had a history of high blood pressure treated with multiple medications. His toxicology results indicated that he had used the blood pressure medications telmisartan, hydrochlorothiazide (HCTZ), and carvedilol. Detected chlorthalidone likely was an impurity in the HCTZ rather than a fourth medication. Although the pilot’s blood pressure medications would not typically be impairing, his high blood pressure conveyed some increased risk of him experiencing an impairing or incapacitating cardiovascular event. However, there is no way to determine whether such an event occurred from the limited autopsy evidence. The combination of tadalafil and alfuzosin use, along with the multiple blood pressure medications, may also have conveyed some increased fainting risk, but this would have depended on multiple unknown variables, as tadalafil and alfuzosin are not typically impairing. Therefore, the only medication detected on postmortem toxicology that had typical impairing effects was chlorpheniramine. Although the measured level of chlorpheniramine in cavity blood could not be reliably related to specific effects, it indicated a possibility that the pilot may have been experiencing some associated sedation or psychomotor slowing. This may have made the pilot more susceptible to falling asleep. Chlorpheniramine effects also may have generally impaired his task performance, although it is less obvious how such impairment would explain the accident circumstances involving an extended period of uneventful flight followed by 3 minutes of unusual flight. Whether the pilot was using chlorpheniramine for a distracting or otherwise impairing condition is unknown. Overall, the pilot had medical conditions and had used medications that were associated with increased risk of impairment or incapacitation. However, there was insufficient medical evidence for the investigation to establish whether the pilot was incapacitated, or, if he was, the specific reason for his incapacitation.
Probable cause
The helicopter’s gradual descent and impact with terrain for reasons that could not be determined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24FA069
- Event ID
- 20231220193546
- Case number
- ERA24FA069
- 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, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2023-12-20.
- API snapshot SHA-256: b0f3136f5e167f27e57c393081242eac0ca2cfa16d33f27161f157e28f42426c; retrieved 2026-09-15T08:09:29.064Z.