FirstAlerts
Plane CrashesVersion 3

Cessna 150 collides with Pennsylvania State Police helicopter near Carlisle; pilot killed

A Cessna 150 struck a hovering Pennsylvania State Police helicopter during a training exercise, killing the Cessna pilot and injuring two helicopter pilots, according to multiple reports.

By AI ReporterFirst reported Aug 20, 2026, 2:26 p.m. ETUpdated Aug 21, 2026, 12:22 a.m. ET
A struck a helicopter that was hovering in mid-air during a training exercise near , Pennsylvania, according to the Philadelphia Inquirer. The plane veered off the north side of the runway for an unknown reason, the outlet reported. The phase of flight is disputed: wgal.com reported the plane was on , while the Inquirer and aerotime.aero reported it was . people were injured and both survived, according to aerotime.aero and the Inquirer. The incident occurred at approximately , wgal.com reported, though the date is in dispute: the Inquirer, aerotime.aero, and nypost.com reported August 19, 2026, while wgal.com reported August 19, 2020. The pilot of the plane was an emergency room doctor at Penn State Health, according to the Inquirer. The pilot was identified as Dr. Paul William Sokoloski, a 57-year-old ER doctor, according to nypost.com. The helicopter's pilots were taken to hospital with minor injuries, according to aerotime.aero. The cause of the incident has not been determined, and the National Transportation Safety Board and the Federal Aviation Administration are investigating, wgal.com reported. An NTSB investigator said there is no immediate explanation for the fatal collision and that it is early in the probe, according to nypost.com. Registry records list the as operating nine aircraft, one of which is a Cessna 208 B registered in the . The aircraft involved in the incident 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 321 Aug 2026, 04:22current

    Updated to include the pilot's name and age, the NTSB investigator's statement, and the conflicting date and phase-of-flight reports.

  2. Version 220 Aug 2026, 19:26

    Added date and phase-of-flight conflicts; noted investigation by NTSB and FAA; clarified registry records.

  3. Version 120 Aug 2026, 17:36

    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.