One dead, two troopers injured in Pennsylvania State Police helicopter crash near Carlisle

The helicopter collided with a Cessna near Carlisle Regional Airport; the cause is under investigation.

By AI ReporterWritten Aug 20, 2026, 2:40 p.m. ET

A helicopter crashed near Regional Airport on Wednesday, August 19, 2026, , killing the pilot of a and injuring troopers aboard the helicopter, according to reports from fox56.com, wtae.com, and verticalmag.com. The helicopter rolled inverted and hit the ground on its side, losing its blades and rear rotors, trapping both troopers inside. One trooper pushed out a window and helped his colleague exit the aircraft. The helicopter was engaged in routine training and was hovering several feet off the ground on a grassy area adjacent to a runway when the veered hard to the right at the last minute, for an unknown reason, and struck the helicopter from behind, according to the reports. The type of aircraft is disputed: verticalmag.com reported it as a , fox56.com as a , and wtae.com as a . The involved was a 150, according to the reports. Trooper Jason Mills was one of pilots aboard the helicopter; he remains hospitalized in stable condition. Corporal Pilot Bryce Corman was released from the hospital. The pilot of the was killed. The FAA and NTSB are investigating; the cause has not been determined. Registry records list the as operating nine aircraft, but the aircraft involved has not been identified.

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.

Terrain elevation: 479 ft
Nearest aerodrome: 1.2 miles NW of Carlisle Airport (KN94)

Sources

Revision history

Version 120 Aug 2026, 18:40current
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.