The U.S. aircraft register, updated daily
Accidents · NTSB DCA18IA265 · Final report

Gulfstream G IV incident near Philadelphia, Pennsylvania, August 11, 2018

On August 11, 2018, a 1989 Gulfstream G IV, registered N619A, was involved in an incident during approach (VFR pattern final) near Philadelphia, Pennsylvania (Philadelphia International airport). It was flown under charter and air-taxi rules (Part 135). No one was hurt; 7 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The flight crew’s misalignment of the airplane with a taxiway instead of the assigned runway, resulting in a low-altitude go-around late in the final approach and reduced separation with the airplanes on the taxiway.

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

What the record shows

Date
August 11, 2018
Place
Philadelphia, Pennsylvania · Philadelphia International · map
Type
Incident
Injuries
No one was hurt; 7 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Gulfstream G IV Undesignat, built 1989 · all G IVs on the register
Registration
N619A · registry record · serial 1123
Damage
Not recorded
Flight
Flight · charter and air-taxi rules (Part 135)

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

Pegasus Elite Aviation flight 19 was on final approach to runway 35 at Philadelphia International Airport, Philadelphia, Pennsylvania. The airplane deviated from the runway 35 centerline about 2.4 miles from the runway 35 threshold and aligned with taxiway E shortly thereafter. The flight crew initiated a low-altitude go-around, arrested the airplane’s descent, and started to climb the airplane about 0.1 mile from the south end of taxiway E. The airplane flew past four airplanes that were on taxiway E. The captain stated that he was flying a visual approach to runway 35 with the area navigation (RNAV) approach for backup. Both flight crewmembers stated that the RNAV needle showed that the airplane was centered during the approach. The captain stated that, as the flight proceeded inbound, the airport lights blended together, and he lost visual contact with the runway at a distance of about 1 to 2 miles out and at an altitude of 500 ft above ground level (agl). The first officer stated that he did not see the approach lights or the runway, and that the captain initiated the go-around 1 mile from the airport while the airplane was at 500 ft agl. Flight data recorder (FDR) and Federal Aviation Administration (FAA) radar data showed that, during go-around procedure, the airplane moved to the right from aligned with the taxiway to between the taxiway and runway, and reached a minimum altitude of 125 ft agl when it was 0.1 mile from the runway 35 threshold, at which point the airplane stopped descending and began climbing. FAA radar data showed that the closest the incident airplane came to the first airplane it passed was about 200 ft vertically. The airplane then flew past the three other airplanes that were on taxiway E while continuing to climb. The flight crewmembers initiated a low-altitude go-around because they did not recognize that the airplane was misaligned with the runway until late in the final approach. As a result, safety margins were severely reduced given the incident airplane’s proximity to the ground before the airplane began climbing and the minimal distance between the incident airplane and the airplanes on taxiway E. The high-intensity runway lights (HIRLs) for runway 35 were on step 1, the same level as the taxiway lights. Both flight crewmembers reported that they called the air traffic control tower to request that the runway light setting be increased, but their request was not heard on the ATC audio recording. The reduced visual cues could have contributed to the flight crew’s delay in identifying the airplane’s misalignment with the intended landing surface. However, sufficient visual cues should have been available to the flight crew to indicate the need for a go-around earlier in the approach, including the presence of four airplanes on a taxiway that was 400 ft to the left of runway 35.

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. Wrong surface or wrong airport during approach (VFR pattern final)
  2. Loss of visual reference during approach (VFR pattern final)
  3. Near midair/TCAS alert/loss of separation during approach (VFR go-around)
  4. Course deviation during approach (VFR pattern final) defining event

The NTSB's findings

  • Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Flight crew
  • Personnel issues › Action/decision › Action › Delayed action › Flight crew

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 12,500 hours in all; 1,400 in this make and model
  • Medical certificate: Unknown
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 10,000 hours in all; 4,000 in this make and model
  • Medical certificate: Unknown
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Landing gear: fixed
  • Engine 1: Rolls-Royc TAY 611SER (turbofan); 0 hours total
  • Engine 2: Rolls-Royc TAY 611SER (turbofan); 0 hours total
  • Operator: Pegasus Elite Aviation

The flight

  • Departed from: MMSD San Jose Del Cabo OF at 8:11 pm
  • Flight plan: IFR
  • Runway 35, 6,501 ft by 150 ft

Weather at the time

  • Light: night
  • Wind: from 290° at 6 knots
  • Sky: broken clouds at 25,000 ft; scat at 18,000 ft
  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Cabi1
Flight crew2
Passengers4

Documents from the investigation the NTSB's docket: the evidence folder behind the report

4 documents, released by the NTSB on March 29, 2024. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Flight Data Recorder - Specialist's Factual Report PDF, 3 pages View Download
2 Flight Data Recorder - Attachment 1 (FDR Tabular Data for Event Flight) data file Download
3 Aircraft Performance Study PDF, 6 pages View Download
4 Flight Crew Interview Summaries PDF, 5 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.