FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA26LA130 · Textron Aviation Inc 680A

27 Feb 2026 · Miami, FL, United States

NetJet Sales Textron Aviation Inc 680A · Accident: aircraft structural failure en route

From an unrecorded airport to Washington Dulles International Airport (IAD)

Report a problem

Event

NTSB case
ERA26LA130
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
Event fatalities
Unknown
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Textron Aviation Inc 680A

Aircraft type
Cessna 680
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N519QS
Operator
NetJet Sales
Onboard fatalities
Unknown
Route
From not recordedTo Washington Dulles International Airport (IAD), Dulles, VA
Aircraft age
About 10 years (built 2016)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Aircraft structural failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The second-in-command (SIC) pilot of the business jet stated that, when beginning to taxi from parking, they felt a “bump”, so he exited the airplane and checked the area around the nose wheel. With no damage noted, he re-entered the airplane and the crew continued to taxi to the active runway for departure. Short of the runway, the SIC stated that he wanted to perform another visual inspection of the airplane prior to departing. Air traffic control granted permission to the flight crew and the SIC performed a visual examination of the airplane, starting at the nose landing gear. He stated that he then did a “standard clockwise” inspection around the airplane, but he did not notice anything out of the ordinary and he proceeded back into the airplane, after which the flight departed. The pilot-in-command (PIC) reported that about 1 hour into cruise flight, he felt something similar to “light turbulence” that escalated into a significant “buffet”. The PIC instructed the SIC to reduce speed and the autopilot was disengaged. Shortly after, the PIC recalled seeing yellow crew alerting system messages regarding nose pitch, which subsequently cleared, briefly reappeared, before clearing for the remainder of the flight. After additional buffeting and concern for a potential trim malfunction, the crew elected to divert the flight to a nearby airport. The diversion, landing, and taxi to parking were uneventful and no additional vibrations or controllability problems occurred. Once parked, the flight crew performed an external walkaround inspection of the airplane and noted that the right elevator was partially detached at the outboard hinge and was bent down by about 30°. A review of security camera footage from the fixed based operator (FBO) at the departure airport showed that the airplane had contacted a jet blast fence, in the vicinity of the right elevator and horizontal stabilizer, while the flight crew were taxiing from parking. Photographs and measurements obtained from the FBO depicted white paint transfer marks on the fence at a height that was consistent with the accident’s airplane’s elevator.

Probable cause

The flight crew’s failure to maintain adequate clearance from the blast fence during taxi to the runway for departure, and their inadequate inspection of the airplane after it contacted the blast fence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA26LA130
Event ID
20260227202563
Case number
ERA26LA130
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 4d1e8320ec25603b568de6c1dac3f29e8dca555e287353a0a5d4a28d73599184; retrieved 2026-09-16T20:52:16.692Z.