Textron Aviation INC 680A accident near Laredo, Texas, June 17, 2026
On June 17, 2026 at about 3:00 am local time, a 2016 Textron Aviation INC 680A, registered N523QS, was substantially damaged in an accident during enroute near Laredo, Texas (Laredo International Airport). It was a personal flight under fractional-ownership rules (Part 91 subpart K). 1 person was killed, 1 person was seriously injured and 4 people had minor injuries. The weather was visual conditions (good weather).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 17, 2026 · about 3:00 am local time
- Place
- Laredo, Texas · Laredo International Airport · map
- Type
- Accident
- Injuries
- 1 person was killed, 1 person was seriously injured and 4 people had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Textron Aviation INC 680A, built 2016
- Registration
- N523QS · registry record · serial 680A0061
- Damage
- Substantial damage
- Flight
- Personal flight · fractional-ownership rules (Part 91 subpart K)
The NTSB's narrative preliminary · quoted from the NTSB record
On June 16, 2026, at 2200 central daylight time, a Textron Aviation Inc 680A, N523QS, sustained substantial damage when it was involved in an accident in Laredo, Texas. The captain received serious injuries, the first officer received minor injuries, one passenger was fatally injured, and three passengers received minor injuries. One person in a moving vehicle received minor injuries. The airplane was operated by NetJets as a Title 14 Code of Federal Regulations Part 91 Subpart K fractional ownership flight. According to the flight crew, early in the flight, they noticed an unusual vibration, which they had not experienced before. They contacted the NetJets Flight Operations Duty Manager (FODM) via telephone and during that initial conversation, the flight crew described the vibration as “a low frequency vibration and a humming noise… it sounds like a fan is on… you can feel it in the dashboard…it was on steady during the climb, but it is gone now.” NetJets maintenance control then joined the call, and the captain provided an update that the vibration “was intermittent for a while and now it is gone.” During the discussion, the flight crew received a Crew Alerting System (CAS) message related to the Air Data Computer (ADC), “BOTH ON ADC 1.” The maintenance controller suggested that the vibration might be caused by an avionics cooling fan in the forward instrument panel. This idea was reinforced by the CAS message. The captain reported that at that time “there are no indications anywhere of anything abnormal on the synopsis pages… the vibration is cycling on and off.” The captain asked, “I don’t know if that’s related? Could that be ADC related to the fan?” The crew accomplished the Quick Reference Handbook procedure for the CAS message, and the message cleared. After further discussion with the maintenance controller and FODM, it was determined that the flight could safely proceed to its planned destination and write-up the vibration once the flight was completed. As the airplane approached the US and Mexico border, the flight crew received a “FUEL BST PUMP ON R” CAS message, which indicated that the right fuel system had low fuel pressure. The message was followed a few seconds later by a “FUEL PRESS LOW R” CAS message, which indicated that the right fuel system pressure was low. About three minutes later, two more CAS messages were displayed: “ELEC TRU FAIL R” and “WSHLD HEAT INOP R”, and about 11 minutes later, a “FUEL LEVEL LOW R” message was displayed. The flight crew declared an emergency with the Monterrey Area Control Center (ACC) and Monterrey ACC handed the flight off to Houston Air Route Traffic Control Center (ARTCC). On the initial check-in with the Houston ARTCC, the flight crew reported a generator failure and “multiple other failures” issues including “fuel level low”. They requested to divert to Laredo International Airport (LRD), Laredo, Texas, and were cleared to LRD via radar vectors. When asked if they were ready for the approach or if they needed time to execute checklists, the flight crew stated that they were ready and requested a visual approach to a 5-mile final for runway 36L. Due to the airplane’s high altitude, the Houston ARTCC vectored the airplane with a right 270-degree turn to establish it on a 14-mile final to runway 36L. While the airplane was on final approach, the right engine flamed out, followed a few seconds later by the left engine. The first officer, who was the pilot monitoring, asked the LRD air traffic control tower (ATCT); “is there a field off to our right?” The LRD ATCT replied “negative, there are no other fields next to you.” The first officer asked, “are there any open pastures or fields off to our right?” LRD ATCT replied, “It’s just going to be the main highway, and that’s just about it.” The flight crew maneuvered the airplane to touch down on the northbound lanes of the Bob Bullock Loop, about one mile southeast of the airport. Videos from several security cameras and doorbell cameras were obtained, which showed two instances of fire flaring up around the airplane as it was on final approach. As the airplane touched down in the northbound lanes of traffic, it sheared off several light poles, struck a vehicle, and came to rest straddling the right-hand edge of an overpass. The airplane fuselage rolled onto its right side with the rear cabin emergency exit on the ground and the main cabin door exit oriented upward. The main cabin door was eventually opened, and five occupants egressed via this exit. The airplane sustained substantial damage to the fuselage, empennage, and both wings. The airplane wreckage was initially recovered to a secure hangar at LRD for preliminary examination. During the examination, flight control continuity was established for the ailerons, elevator, and rudder. Further examination revealed that the right engine fuel pressure switch (part number 9914488-2) was found separated from the fuel tube assembly (part number 6956100-118) and the fuel tube assembly was fractured adjacent to the weld joint for the attachment tube leading to the fuel pressure switch as shown in Figure 1. Multiple P-clamps on the fuel tube assembly were also found fractured as shown in Figure 2. Figure 1. Right engine fuel tube assembly and fuel pressure switch Figure 2. Fractured fuel tube assembly P-clamps The right engine starter generator (part number 9914685-1; model number 23291-005; serial number P3825) was manufactured by Safran in October 2023. The starter generator was missing multiple screws from the outer housing as shown in Figure 3. The starter generator had 57.2 hours of time remaining since its last overhaul that was performed on April 25, 2025; the overhaul interval was 1,200 hours. Figure 3. Right engine starter generator and missing screws (red circles) Upon removal of the starter generator, the starter generator shaft was found bent, the cooling fan was fractured, and multiple cooling fan blades and ball bearings were found when the generator was removed. The cooling fan shroud also contained circumferential scoring marks. The fuel tube assembly, starter generator, and multiple components were sent to the NTSB Materials Laboratory in Washington, DC, for further examination. The airplane was equipped with a flight data recorder and a cockpit voice recorder. Both units were sent to the NTSB Recorders Laboratory in Washington, DC, for further examination and download of pertinent data. The airplane wreckage was relocated to a secure facility for further examination.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Powerplant sys/comp malf/fail during enroute defining event
- Electrical system malf/failure during enroute
- Loss of engine power (partial) during enroute
- Fuel exhaustion during approach
- Loss of engine power (total) during approach
The aircraft
- Airframe total time: 9,371.5 hours
- Last inspection: continuous airworthiness programme, February 14, 2026
- Maximum gross weight: 30,800 lb
- Seats: 9
- Landing gear: fixed
- Fire in flight and on the ground
- Operator: Netjets Aviation, Inc
The flight
- Departed from: MMSD Los Cabos at 1:19 am
- Destination: KAUS Austin TX
- Flight plan: IFR
- A second pilot was aboard
Weather at the time
- Light: night
- Wind: from 110° at 2 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 82°F (28°C), dew point 75°F (24°C)
- Altimeter: 29.75 inHg
- Observation at 9:56 pm from LRD, 2 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flig | 1 | 1 | ||
| Passengers | 1 | 3 |
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number CEN26FA228.
