The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB ERA26LA130 · Final report

Textron Aviation INC 680A accident near Miami, Florida, February 27, 2026

On February 27, 2026 at about 4:00 pm local time, a 2016 Textron Aviation INC 680A, registered N519QS, was substantially damaged in an accident during enroute (cruise) near Miami, Florida (Miami Intl airport). It was a positioning flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. 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 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.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 27, 2026 · about 4:00 pm local time
Place
Miami, Florida · Miami Intl · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Textron Aviation INC 680A, built 2016
Registration
N519QS · registry record · serial 680A-0054
Damage
Substantial damage
Flight
Positioning flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

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

  1. Collision with terrain or object (not controlled flight into terrain) during taxi (to runway)
  2. Aircraft structural failure during enroute (cruise) defining event

The NTSB's findings

  • Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Flight crew
  • Environmental issues › Physical environment › Object/animal/substance › Fence/fence post › Awareness of condition
  • Personnel issues › Task performance › Inspection › Preflight inspection › Flight crew
  • Aircraft › Aircraft systems › Flight control system › Elevator control system › Damaged/degraded

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; instrument: airplane
  • Flight time: 17,832 hours in all; 3,195 in this make and model; 95 in the last 90 days; 35 in the last 30 days
  • Last flight review: January 30, 2026
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; instrument: airplane
  • Flight time: 3,651 hours in all; 1,584 in this make and model; 142 in the last 90 days; 57 in the last 30 days
  • Last flight review: January 16, 2026
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 8,959 hours
  • Last inspection: approved inspection programme, February 21, 2026
  • Maximum gross weight: 30,800 lb
  • Seats: 10
  • Landing gear: retractable
  • Engine 3: P&W Canada PW306D1 (turbofan); 6,632 hours total
  • Engine 4: P&W Canada PW306D1 (turbofan); 6,828 hours total
  • Operator: Netjet Sales Inc

The flight

  • Destination: IAD Dulles VA
  • Flight plan: IFR
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 120° at 9 knots, gusting 17
  • Visibility: 10 statute miles
  • Sky: scat at 1,900 ft
  • Temperature: 81°F (27°C), dew point 70°F (21°C)
  • Altimeter: 30.05 inHg
  • Observation at 10:53 am from MIA, 2 miles away

Weather report (METAR): METAR KMIA 271553Z 12009G17KT 10SM SCT019 27/21 A3005 RMK AO2 SLP175 T02670211 $=

Injuries

FatalSeriousMinorNone
Flig2

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 ERA26LA130.