One dead in midair collision between Cessna 150 and Pennsylvania State Police helicopter
A Cessna 150 and a Pennsylvania State Police Bell 407 helicopter collided near Carlisle Regional Airport on August 19, 2026, killing the Cessna pilot and injuring two troopers.
2 reports on this incident · first at Sep 5, 2026, 9:52 p.m. ET
Earlier reports
Sep 5, 2026, 9:52 p.m. ETFirst report
Cessna 150 and Pennsylvania State Police Helicopter Collide Near Carlisle
A Cessna 150 and a Pennsylvania State Police helicopter collided near Carlisle Regional Airport on Wednesday, August 19, 2026, at around 6:50 p.m., according to fox29.com and fox5dc.com. Two people survived the collision, the outlets reported. The helicopter was conducting a hover taxi training maneuver, and the Cessna pilot was a certified flight instructor, according to the reports. The helicopter was struck from behind by the Cessna, which hit the helicopter's tail rotor and main rotor, the outlets reported.
The National Transportation Safety Board (NTSB) is leading the investigation, with support from the Federal Aviation Administration and Pennsylvania State Police, according to fox5dc.com. The NTSB arrived at Carlisle Airport early Thursday to begin investigating the collision, fox29.com reported. The cause of the collision has not been determined. The wreckage will be moved to Clayton, Delaware for investigation, according to the outlets.
The aircraft involved has not been identified. Registry records list Pennsylvania State Police as operating nine aircraft, one of which is a Cessna 150; however, that record does not identify the aircraft involved in this incident.
Was this report accurate and useful?
Reference data
From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.
- Registration
- N23330
- Type
- Cessna 150H — single-engine piston landplane
- Engines
- CONT MOTOR 0-200 SERIES
- Registered owner
- Langeard Aviation IncThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
- Terrain elevation
- 479 ft
- Nearest aerodrome
- 1.2 miles NW of Carlisle Airport (KN94)
Sources
- Pilot killed, 2 PSP Troopers hurt after aircraft collision, officials saynbcphiladelphia.com
- Pilot killed, 2 troopers injured after helicopter, small plane crash at Carlisle airportfox29.com
- Small plane and police helicopter crash in midair at PA airportdailymail.com
- Cessna 150 Pilot Killed, 2 Troopers Hurt In Midair Crash With State Police Helicoptersimpleflying.com
- NTSB reveals what happened in the moments leading up to deadly plane, helicopter crashnbcphiladelphia.com
- Pilot killed, 2 troopers injured after helicopter, small plane crash at Carlisle airportfox5dc.com
- Cessna 150, Police Helicopter Collide in Pennsylvaniaavweb.com
- 1 Dead in Midair Involving Police Helicopter and Cessnaflyingmag.com
- Pilot killed in collision with Pennsylvania State Police helicopter identifiedfox29.com
- NTSB investigators recover data cards in deadly Carlisle Airport crashnbcphiladelphia.com
- Recent Fatal Chopper Crash First Since '89 for Pennsylvania State Police Aviation firehouse.com
- NTSB report details fatal collision involving Pennsylvania State Police helicopter and airplanekcra.com
- NTSB finds no mechanical issues in Pa. midair collisionwishtv.com
- 'Violent crash': What we know about deadly plane vs. helicopter crash at Carlisle Regional Airport6abc.com
- Pennsylvania crash: One killed in ‘violent’ collision between Cessna 150 and police helicoptertimesofindia.indiatimes.com
- Pilot killed after light aircraft crashes into police helicopter in Pennsylvaniaindependent.co.uk
- Pilot killed in violent collision with Pennsylvania police helicopterky3.com
- Airplane pilot killed in collision with Pennsylvania police helicopter near runwaywral.com
Revision history
- Version 38 Sept 2026, 09:52current
Updated to reflect the published status and incorporate the latest reporting on the investigation and wreckage removal.
- Version 26 Sept 2026, 02:53
Added identification of the Cessna as N23330 with registered owner, added operator fleet context, and clarified that the aircraft involved has not been identified by authorities.
- Version 26 Sept 2026, 01:52current
Updated to reflect that the NTSB is leading the investigation per fox5dc.com, while fox29.com reports the NTSB arrived Thursday; added detail on the collision sequence and wreckage move.
- Version 16 Sept 2026, 02:23
First published.
- Version 13 Sept 2026, 08:08
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.