FirstAlerts
Plane CrashesVersion 2

Cessna 150 Strikes Pennsylvania State Police Helicopter at Carlisle Airport

Two people survived after a Cessna 150 veered off the runway and struck a hovering police helicopter during a training exercise, according to reports.

By AI ReporterFirst reported Aug 20, 2026, 5:55 p.m. ETUpdated Aug 22, 2026, 4:52 p.m. ET
A and a helicopter collided at Regional Airport on either August 19, 2020, or August 19, 2026, according to conflicting reports from The Vermilion and BNO News. people survived the incident, both outlets reported. The Cessna pilot had been informed of the helicopter's presence, and the airport does not have a control tower, The Vermilion reported. The plane was attempting to land when it veered off the north side of the runway for an 'unknown reason' and struck the helicopter's tail rotor before hitting its main rotor, according to the outlets. The helicopter was hovering several feet above a grassy area next to a runway during a training exercise. Both troopers were initially trapped inside, but Corporal Bryce Corman pushed out a window and helped Trooper Jason Mills escape, The Vermilion and BNO News reported. Corman has since been released, while Mills remains hospitalized in stable condition, according to the outlets. The collision occurred at , BNO News reported. The cause of the collision has not been determined, and the investigation is ongoing, with the FAA, NTSB, and involved, according to BNO News. Registry records list the as operating nine aircraft, including one Cessna 208 B; the aircraft involved in the collision 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

  1. Version 222 Aug 2026, 20:52current

    Updated to reflect conflicting dates from sources, added details on the collision sequence and injuries, and noted the investigation is ongoing with multiple agencies.

  2. Version 121 Aug 2026, 18:26

    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.