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

Gulfstream Aerospace G-IV accident near Fort Lauderdale, Florida, August 21, 2021

On August 21, 2021 at about 5:40 pm local time, a 1989 Gulfstream Aerospace G-IV, registered N277GM, was substantially damaged in an accident near Fort Lauderdale, Florida (Fort Lauderdale Executive airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 14 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 pilot-in-command’s (PIC) and second-in-command’s (SIC) failure during preflight inspection to ensure that the nose landing gear’s pip pin was properly installed, which resulted in separation of the pip pin during takeoff. Contributing to the accident was the ground crew supervisor’s failure to inform the PIC or SIC of the anomaly concerning the pip pin following a towing operation.

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

What the record shows

Date
August 21, 2021 · about 5:40 pm local time
Place
Fort Lauderdale, Florida · Fort Lauderdale Executive · map
Type
Accident
Injuries
No one was hurt; 14 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Gulfstream Aerospace G-IV NO SERIES, built 1989 · all G-IVs on the register
Registration
N277GM · no longer on the register · serial 1124
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The flight crew, which consisted of the pilot- and second-in-command (PIC and SIC), and a non-type-rated observer pilot, reported that during takeoff near 100 knots a violent shimmy developed at the nose landing gear (NLG). The PIC aborted the takeoff and during the abort procedure, the NLG separated. The airplane veered off the runway, and the right wing and right main landing gear struck approach lights, which resulted in substantial damage to the fuselage and right wing. The passengers and flight crew evacuated the airplane without incident through the main cabin door. Postaccident interviews revealed that following towing operations prior to the flight crew’s arrival, ground personnel were unable to get the plunger button and locking balls of the NLG’s removable pip pin to release normally. Following a brief troubleshooting effort by the ground crew, the pip pin’s plunger button remained stuck fully inward, and the locking balls remained retracted. The ground crew re-installed the pip pin through the steering collar with the upper torque link arm connected. However, with the locking balls in the retracted position, the pin was not secured in position as it should have been. Further, the ground personnel could not install the safety pin through the pip pin because the pin’s design prevented the safety pin from being inserted if the locking balls and plunger were not released. The ground personnel left the safety pin hanging from its lanyard on the right side of the NLG. The ground personnel subsequently informed their ramp supervisor of the anomaly. The supervisor reported that he informed the first arriving crewmember at the airplane (the observer pilot) that the nose pin needed to be checked. However, all three pilots reported that no ground crewmember told them about any issues with the NLG or pins. Examination of the runway environment revealed that the first item of debris located on the runway was the pip pin. Shortly after this location, tire swivel marks were located near the runway centerline, which were followed by large scrape and tire marks, leading to the separated NLG. The safety pin remained attached to the NLG via its lanyard and was undamaged. Postaccident examination and testing of the NLG and its pins revealed no evidence of preimpact mechanical malfunctions or failures. The sticking of the pip pin plunger button that the ground crew reported experiencing could not be duplicated during postaccident testing. When installed on the NLG, the locking ball mechanism worked as intended, and the pip pin could not be removed by hand. Although the airplane’s preflight checklist called for a visual check of the NLG’s torque link to ensure that it was connected to the steering collar by the pip pin and that the safety pin was installed, it is likely that none of the pilots noticed that the pip pin did not have its safety pin installed during preflight. Subsequently, during the takeoff roll, without the locking balls extended, the pip pin likely moved outward and fell from its position holding the upper torque link arm. This allowed the upper torque link arm to move freely, which resulted in the violent shimmy and NLG separation. The location of the debris on the runway, tire marks, and postaccident examination and testing support this likely chain of events. Contributing to the PIC and SIC’s omission during preflight was the ground crew’s failure to directly inform the PIC or SIC that there was a problem with the NLG pip pin. The ground crew also failed to discard the malfunctioning pip pin per the airplane’s ground handling procedures and instead re-installed the pip pin. Although the observer pilot was reportedly informed of an issue with a nose gear pin, he was not qualified to act as a required flight crewmember for the airplane and was on his cell phone when he was reportedly informed of the issue by the ramp supervisor. These factors likely contributed to the miscommunication and the PIC’s and SIC’s subsequent lack of awareness of the NLG issue.

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. 301300 during 301
  2. 100030 during abrupt maneuver
  3. 300330 during nose over
  4. 301338 during 301

The NTSB's findings

  • Personnel issues › Task performance › Communication (personnel) › Lack of communication › Ground crew
  • Personnel issues › Task performance › Use of equip/info › Use of checklist › Flight crew
  • Personnel issues › Task performance › Inspection › Preflight inspection › Flight crew
  • Personnel issues › Experience/knowledge › Experience/qualifications › Total experience w/ equipment › Copilot
  • Personnel issues › Experience/knowledge › Knowledge › Knowledge of equipment › Copilot

Pilot

  • Ratings: multi-engine land, single-engine land, none, APLN, helicopter
  • Flight time: 20,053 hours in all; 3,120 in this make and model; 184 in the last 90 days; 49 in the last 30 days; 17,900 as pilot in command
  • Last flight review: November 2, 2020
  • Medical certificate: class 1
  • Injury: no injuries

Co-pilot

  • Ratings: multi-engine land, single-engine land, ASE, APLN, none
  • Flight time: 1,617 hours in all; 204 in this make and model; 32 in the last 90 days; 0 in the last 30 days; 943 as pilot in command
  • Last flight review: July 15, 2021
  • Medical certificate: class 1
  • Injury: no injuries

The aircraft

  • Airframe total time: 12,990 hours
  • Last inspection: continuous airworthiness programme, June 4, 2021
  • Maximum gross weight: 75,000 lb
  • Seats: 22
  • Landing gear: retractable
  • Engine 1: Rolls-Royc TAY MK 610-8 (turbojet); 12,382 hours total
  • Engine 2: Rolls-Royc TAY MK 610-8 (turbojet); 12,599 hours total
  • Operating certificate: in the vicinity

The flight

  • Departed from: FXE Fort Lauderdale FL at 5:40 pm
  • Destination: LAS Las Vegas NV
  • Flight plan: IFR
  • Runway 09/2, 6,002 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 130° at 9 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 93°C, dew point 73°C
  • Altimeter: 29.99 inHg
  • Observation at 1:53 pm from FXE

Weather report (METAR): KFXE 211753Z 13009KT 10SM CLR 34/23 A2999 RMK AO2 SLP156 T03390228 10339 20283 58002

Injuries

FatalSeriousMinorNone
Flig4
Passengers10

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