![]()
On June 16, 2026, a Cessna 680A Citation Latitude (N523QS) operated by NetJets crashed in Laredo, Texas. The crash killed one passenger and injured 6 others. The NTSB has released its preliminary report on the accident that include a series of CAS messages indicating multiple component failures.Preliminary Findings The report states the crew experienced an unusual vibration and received a CAS message related to the Air Data Computer (ADC), "BOTH ON ADC 1." The NetJets maintenance controller suggested that the vibration might be caused by the avionics cooling fan in the forward instrument panel. After the message was cleared, they continued with the planned flight. Later, they received multiple CAS messages indicating low fuel system pressure, loss of power and failure of other systems on the right side of the aircraft. The crew declared an emergency and requested to divert to Laredo International Airport (LRD). After being cleared for the approach, the crew requested a visual approach to Runway 36L with a five-mile final. While on final approach, both engines reportedly caught fire. Unable to land at the airport and with no nearby fields or pastures, the aircraft touched down one mile from LRD on northbound lanes of the Bob Bullock Loop. While examining the wreckage, investigators discovered that the right engine fuel pressure switch (part number 9914488-2) had separated from the fuel tube assembly (part number 6956100-118) and multiple P-clamps on the fuel tube assembly had fractured. The starter generator (part number 9914685-1) was also missing multiple screws from the outer housing. Once removed, the generator shaft was bent, the cooling fan was fractured, and multiple cooling fan blades and ball bearings were found loose. The cooling fan shroud also contained circumferential scoring marks. From parts list to propable causeWhat the report shares is the sequence and a set of components: a vibration the crew cleared, then fuel-pressure and power losses down the right side, then both engines burning on final, then a touchdown a mile short on the Bob Bullock Loop. But a report of failed parts is not probable cause.NTSB investigators will run metallurgical exams on the fractured items along with a starter-generator tear down. What needs to be establish is which of those failures came first. That's something a failed parts list cannot answer. NTSB final report timelines typically run from 12 to 24 months. Until then, a determination of probable cause will have to wait.