Envoy Air Flight AA-3927 Identified as Embraer E175LR After Fuel Emergency
The aircraft involved in the August 11 fuel emergency has been identified as an Embraer E175LR, registration N285NN, according to paddleyourownkanoo.com.
2 reports on this incident · first at Aug 22, 2026, 9:16 p.m. ET
Earlier reports
Aug 22, 2026, 9:16 p.m. ETFirst report
Envoy Air Flight Declares Fuel Emergency After Three Failed Landing Attempts
An Envoy Air flight, operating as American Airlines flight AA-3927, declared a fuel emergency on August 11, 2026, after three failed landing attempts at Lexington and Louisville due to severe thunderstorms, according to paddleyourownkanoo.com. The aircraft, an Embraer E175LR with registration N285NN, squawked 7700 to indicate an emergency and landed safely at Evansville Regional Airport after three hours in the air. The plane had just 30 minutes of fuel left when the emergency was declared.
Registry records list the registered owner as American Airlines Inc; the owner of record is not necessarily the operator of the flight. The aircraft is an Embraer S A ERJ 170-200 LR, according to aircraft registry records. The NTSB database lists nine other cases involving this aircraft type since 2008, none of which involved a fatality; this record says nothing about the cause of this incident.
The cause of the fuel emergency has not been determined. The investigation is ongoing.
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
- N285NN
- Type
- Embraer S A ERJ 170-200 LR — twin-engine jet landplane
- Engines
- GE CF34-8E5
- Operator of record
- American Airlines
- Registered owner
- American Airlines IncThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
- Terrain elevation
- 404 ft
- Nearest aerodrome
- 3.1 miles SSE of Skylane Airport (3EV)
Sources
Revision history
- Version 123 Aug 2026, 01:22current
First published.
- Version 123 Aug 2026, 01:16current
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.