FirstAlerts
Plane CrashesVersion 3

NTSB Investigating Fatal NetJets Citation Latitude Accident Near Laredo, Texas

One of six people on board was killed in the June 17, 2026 accident involving N523QS, according to the National Transportation Safety Board accident record; the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 11:34 a.m. ET
One person was killed in an accident involving a near Laredo, Texas, on June 17, 2026, according to the National Transportation Safety Board accident record. The event is developing and details remain limited. The accident record lists people on board and one fatality, gives the time as about 3:00 a.m. local time, and names the operator as . and the aircraft as . The NTSB is investigating. The cause has not been determined. Aircraft registry records list as a twin-engine jet landplane, serial number 680A0061, powered by Pratt & Whitney Canada PW306D1 engines, first flown in 2016 and 10 years old, registered in the United States. The registry lists the registered owner as Netjets Sales Inc; the owner of record is not necessarily the operator of the flight, the pilot, or otherwise connected to it. Corporate and regulatory filings describe Netjets Sales, Inc. as a Columbus, Ohio-based entity within the NetJets group — whose parent, NetJets Inc., is described in Berkshire Hathaway filings as a provider of fractional aircraft ownership programs — and business directories classify it as a wholesaler of aircraft and parts and a "lessee of tangible property." A Florida corporate filing lists Adam Johnson as chairman of NetJets Sales, Inc.; a Wikipedia entry lists Patrick Gallagher as president of NetJets Aviation. The investigation has made no finding connecting any post-holder to this accident. As a matter of record only, and saying nothing about the cause here, the NTSB database lists five other cases involving the same owner or operator: N168QS, a Bombardier BD-700-1A10, at Atlantic City, New Jersey on May 24, 2026 (ENG26LA023); N247QS, a Bombardier CL-600-2B16, at Jackson, Wyoming on November 17, 2024 (WPR25LA045); N378QS, a Cessna 680, at Wilmington, Delaware on September 3, 2017 (GAA17CA520); N304QS, an Embraer EMB-505, at Dallas, Texas on April 7, 2016 (OPS16IA008); and N900QS, a Cessna 750, at Miami, Florida on April 12, 2015 (OPS15IA017). For the type, the database — which begins in 2008 — contains two other cases, of which none involved a fatality. Neither count bears on this accident. Geographic reference data places Laredo in Webb County, Texas, at a settlement elevation of 430 feet, 3.7 miles southwest of Laredo International Airport (KLRD), 5.9 miles northeast of Quetzalcóatl International Airport (MMNL) and 14 miles north of Rancho Blanco Airport (TE32); that locates the city, not the accident site, and says nothing about what happened. The NTSB investigation remains 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
N523QS
Type
Textron Aviation Inc 680A — twin-engine jet landplane
Engines
P&W CANADA PW306D1
Built
2016-01-01 (10 years old)
Registered owner
Netjets Sales IncThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.
Terrain elevation
430 ft
Nearest aerodrome
3.7 miles SW of Laredo International Airport (KLRD/LRD)

Sources

Revision history

  1. Version 37 Aug 2026, 15:34current

    Clarified that the geographic reference data locates the settlement rather than the accident site; headline and dek sharpened, no factual changes.

  2. Version 25 Aug 2026, 15:01

    Corrected the local time to about 3:00 a.m. and fixed the reversed compass bearings from Laredo to the three nearby aerodromes.

  3. Version 15 Aug 2026, 14:59

    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.