Plane CrashesVersion 2

Flight School Piper Lands on Interstate 10 Near Pensacola After Reported Oil-Pressure Problem

Two people aboard the single-engine trainer were uninjured in the August 3 emergency landing, according to Aerotime; the FAA investigation remains open and no new details have been released since.

2 reports on this incident · first at Aug 7, 2026, 9:44 a.m. ET

By AI ReporterFirst reported Aug 5, 2026, 12:22 p.m. ETUpdated Aug 7, 2026, 9:45 a.m. ET

A Piper PA-28-151 Cherokee Warrior operated by made an emergency on the eastbound lanes of Interstate 10 near , Florida, on August 3, 2026, at , according to Aerotime. people were on board and no one was injured, Aerotime reported. Aerotime's account remains the most recent reporting available on the ; no further information has been published since it appeared. The FAA has confirmed that the pilot reported an oil-pressure problem but has not released further details about the mechanical failure, Aerotime reported. The cause has not been determined and the investigation remains open. According to Aerotime, the pilot initially attempted to return to International Airport before saying, "We are not making the airport." The aircraft came down on the highway, passing beneath an overhead sign and between moving vehicles; dashcam video of the was recorded by truck driver Eric Jordan, who slowed to create space. Aerotime reported that the flight instructor, Emily Shelton, 21, was flying with a student on his first lesson, and that WEAR News reported she had logged around 1,300 flight hours before the incident. The aircraft was identified as . Aircraft registry records list it as a 1974 Piper PA-28-151, a single-engine piston landplane with a Lycoming O-320 series engine, serial number 28-7415297, 52 years old and registered in the United States. The registry lists the registered owner as Stingray LLC; the owner of record is not necessarily the operator of the flight, the pilot, or otherwise connected to it. No source could be located documenting an aviation organisation of that name at or near . A registry listing for a "Stingray LLC" owning carries a Kalispell, Montana address, according to FlightAware's registration records; it has not been established that this is the same entity, and no details from it are attributed here. Weather observations recorded at International Airport, about 4 miles away and minutes from the reported time, show wind variable at 6 knots, visibility 10 statute miles, few clouds at 3,300 feet and a temperature of 83\u00b0F. As a matter of record, the NTSB database, which begins in 2008, contains 29 other cases involving the Piper PA-28-151, of which 5 involved a fatality; that count says nothing about the cause of this event.

Earlier reports

Aug 7, 2026, 9:44 a.m. ETFirst report
Piper PA-28 Makes Emergency Landing on Interstate 10 Near Pensacola; No Injuries Reported
An aircraft that made an emergency landing on the eastbound lanes of Interstate 10 near Pensacola, Florida, on August 3, 2026 has been identified as N41622, a 1974 Piper PA-28-151 Cherokee Warrior operated by Pensacola Air Flight School, according to aerotime.aero. The landing took place at around 10:55 local time with two people on board, and aerotime.aero reported no injuries.
The cause has not been determined. The FAA has confirmed that the pilot reported an oil-pressure problem but has not released further details about the mechanical failure, according to aerotime.aero. The pilot initially tried to return to Pensacola International Airport before saying "We are not making the airport," aerotime.aero reported, and the aircraft passed beneath an overhead highway sign and between moving vehicles as it landed. Dashcam video of the landing was recorded by truck driver Eric Jordan, who slowed to create space. aerotime.aero reported that flight instructor Emily Shelton, 21, was flying with a student on his first lesson, and that WEAR News reported she had logged around 1,300 flight hours before the incident.
Aircraft registry records list N41622 as a Piper PA-28-151, a single-engine piston landplane with a Lycoming O-320 series engine, serial number 28-7415297, built in 1974 and 52 years old at the time. The registry lists the registered owner as Stingray Llc; the owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight. No source could be located documenting an aviation organisation of that name at or near Pensacola; a separate registry listing for a "STINGRAY LLC" carries a Kalispell, Montana address, and it cannot be established that this is the same entity.
Weather observed at Pensacola International Airport, four miles away and two minutes from the reported time, recorded wind variable at 6 knots, visibility 10 statute miles, few clouds at 3,300 feet and 83°F. That is an instrument reading and not a statement about what happened.
As a matter of record, the NTSB database, which begins in 2008, contains 29 other cases involving the Piper PA-28-151, of which five involved a fatality. That count describes the type and says nothing about the cause of this event. The FAA investigation is open.

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: N41622
Type: Piper PA-28-151 — single-engine piston landplane
Engines: LYCOMING 0-320 SERIES
Built: 1974-01-01 (52 years old)
Registered owner: Stingray LlcThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Terrain elevation: 66 ft
Nearest aerodrome: 4.0 miles SSW of Pensacola International Airport (KPNS/PNS)

Sources

Revision history

Version 47 Aug 2026, 13:44current
No new facts; added the FlightAware registry listing to sources and minor wording tightening.
Version 37 Aug 2026, 12:43
Added headline and dek framing the FAA investigation; body unchanged in substance, with the FlightAware registry listing now cited.
Version 25 Aug 2026, 20:37
Reordered to lead with the FAA's stated oil-pressure account ahead of registry detail, added headline and dek, and labelled the airport weather reading as an instrument measurement.
Version 27 Aug 2026, 13:45current
Deleted the sentence "The event is developing and details may change," which presented a story with no source newer than roughly 44 hours as live. Replaced it with an accurate statement that Aerotime's account is the most recent reporting available and that nothing further has been published since. Added the same qualification to the dek. All facts, figures, quotations and attributions are unchanged.
Version 15 Aug 2026, 17:24
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.