NTSB Preliminary Report: Pennsylvania State Police Bell 407 Collides with Cessna 150H at Carlisle Airport — They Talked on the Radio, So Why Did They Still Collide? — Three Warnings for Air Medical Operations at Small Airports

Published: September 22, 2026  |  Category: Industry

Per a report by Vertical Mag (September 4, 2026), the leading U.S. rotorcraft industry publication, the National Transportation Safety Board (NTSB, docket ERA26FA309) has released its preliminary report on the August 19, 2026 collision at Carlisle Airport, Pennsylvania: a Pennsylvania State Police (PSP) Bell 407 helicopter performing flight instruction training exercises collided with a private Cessna 150H — the airplane's pilot was killed and the two troopers inside the helicopter were seriously injured. This did not happen in crowded metro airspace; it happened in the surface/low-altitude environment of a small general aviation airport, and the two crews had just communicated by radio before the accident. That is exactly why this preliminary report matters so much to the air medical sector: medical helicopters operate at precisely these kinds of small airports at high frequency, and the operating logic — "talking is not the same as seeing, and seeing is not the same as avoiding" — deserves to be chewed over by every HEMS crew.

1. The 30-Second Sequence: Three Key Moments on Security Camera

The NTSB used footage from three airport security cameras to reconstruct the sequence. Before the accident, the PSP Bell 407 crew was performing flight instruction training exercises at the airport: it flew a straight-in approach to the runway, then slowly descended and transitioned to a hover taxi, exiting the paved surface to the north over a grass-covered field. As the helicopter approached the airport, the helicopter crew and the airplane pilot communicated by radio — a witness heard the transmissions, and PSP crew statements confirm: one of the helicopter pilots told the airplane pilot to extend his approach downwind, and the airplane pilot acknowledged and said he was number two for landing. But the cameras show the Cessna 150H crossing the airport threshold while the helicopter was still over the runway — about 30 seconds after the helicopter had done so. "The airplane's wings rocked to the left and right as the airplane flew low over the runway surface, and it appeared to make several lateral and vertical movements as it flew over the runway with the flaps extended," the report states. The airplane never touched down; it continued to fly along the runway, wings rocking, before pitching up and climbing about 1.5 wingspans above the runway. The right wing then dropped and the airplane turned right and descended — toward the helicopter, which by then had transitioned over the grass field. The helicopter pilots said that due to their position and orientation, they did not see the approaching airplane behind them. About eight seconds after the helicopter had left the runway surface, the airplane hit it from behind, striking the tail rotor and main rotor blades. The airplane separated into four major sections, coming to rest across an area of about 250 feet; the helicopter's main rotor blades and tail boom separated, but the main wreckage remained relatively intact and fell onto its left side. The NTSB's postaccident examination showed no sign of any mechanical issues or failures that would have stopped either aircraft from operating normally before the crash; it also noted the airplane's flap actuators were in the retracted position. The investigation is ongoing, and the final report will determine the probable cause.

2. They Talked on the Radio — So Why Did They Still Collide? Three Human-Factors Questions

1) "Reporting your position" ≠ "shared situational awareness." The Cessna pilot acknowledged the request to extend his downwind on the radio and reported number two for landing — the communication chain was complete. But the cameras show he then crossed the threshold and never touched down: an approach that never stabilized and stayed low with rocking wings was, in essence, a go-around on the edge of control. For the helicopter crew, a voice on the radio saying "I'm number two" is no substitute for visually confirming where that airplane actually is and what it is actually doing. 2) A helicopter on a hover taxi has its back to the traffic. As the Bell 407 transitioned over the grass field its nose was pointed away from the runway; any fixed-wing aircraft closing rapidly from behind sat in a visual blind spot. Helicopter cockpits offer excellent visibility, but attention is naturally allocated forward — which is precisely why, after the DCA mid-air, the NTSB is pushing cockpit traffic displays via ADS-B In: to give crews "eyes in the back." Our September 21 report on the FAA implementing the NTSB's DCA recommendations covered regulatory tightening at large airports; Carlisle is the reminder that collisions happen at small airports too — often with no controller in the tower at all. 3) Airport video became the key investigative tool — because there is no "system backstop" for helicopter/fixed-wing separation. At non-towered or lightly staffed airports, separation between helicopters and fixed-wing traffic rests entirely on mutual visual scanning and radio discipline. The security footage helped the NTSB reconstruct the timeline, but cameras cannot prevent collisions. What prevents them is procedure: systematic scanning of the final approach path before and during a hover taxi, physical separation between fixed-wing go-around paths and helicopter operating areas, and the defensive mindset of always assuming the other crew has not seen you.

3. Three Takeaways for the Air Medical Sector

1) HEMS bases are mostly at small airports — the Carlisle lessons transfer directly. The operating profile of medical helicopters — frequent takeoffs and landings at general aviation airports, hover taxiing, mixed operations with training flights and private flying — overlaps heavily with this accident's scenario. As China's low-altitude economy advances, more medical helicopter bases are being established at general aviation airports, and the mixing density of training flights and medical flights will only rise. Operators' manuals should be explicit: at mixed-use airports, helicopter crews must systematically scan the pattern before and during hover taxi and landing, and proactively broadcast position and intentions on the radio; for fixed-wing traffic that has been "acknowledged," visual verification remains mandatory. 2) When evaluating carriers, safety details beyond "the aircraft type" matter just as much. The Bell 407 is one of the world's workhorses of air medical and law enforcement aviation, and this accident had nothing to do with the type — neither aircraft had any mechanical failure. Institutions commissioning medical transport would do better to look past airframe vintage and examine the operator's airport operating procedures: whether risk surveys have been done at frequently used landing sites, and whether coordination mechanisms exist with other airport users (flight schools, private owners). 3) "Radio confirmation" cannot substitute for separation assurance — a law of physics that applies in China and the U.S. alike. The same logic underpins CAAC's low-altitude flight service support system: no matter how air traffic technology evolves, the last line of defense is always crew situational awareness and procedural discipline. The New Mexico air ambulance GPS-jamming crash we covered on September 9 was about the risk of signals being jammed; the September 21 DCA follow-up was about regulatory tightening in large airspace; this article completes the set with mixed operations at small airports — together, the three form the complete picture of 2026 U.S. helicopter safety.

Disclaimer: All facts in this article come from Vertical Mag's report "NTSB releases preliminary report on Cessna 150H collision with Pennsylvania State Police helicopter" (September 4, 2026, verticalmag.com) on the NTSB preliminary report (docket ERA26FA309), accessed and verified on September 22, 2026. Sequence-of-events details are as stated in the NTSB preliminary report; the probable-cause determination rests with the NTSB's final report (the investigation is ongoing, and this article makes no inferential findings as to the cause of the accident). Information on the condition of the PSP crew is subject to official announcements. This article is an industry news share and does not constitute medical, legal or investment advice; in an emergency, call your local emergency number immediately.