Pegasus Elite Aviation Flight 19
Gulfstream G IV Undesignat · Incident: course deviation on approach
From Los Cabos International Airport (MMSD) to an unrecorded destination
Event
- NTSB case
- DCA18IA265
- 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
- Incident
- 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
- API-reported fatalities
- 0 · all aircraft and ground
- 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
- Charter & commuter
- 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
Gulfstream G IV Undesignat
- Aircraft type
- Gulfstream G
- 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
- N619A
- Operator
- Pegasus Elite Aviation
- Onboard fatalities
- Unknown
- Route
- From Los Cabos International Airport (MMSD), San Jose del CaboTo not recorded
- Aircraft age
- About 29 years (built 1989)
- 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 135: Air Taxi & Commuter
- 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
- Approach · VFR pattern final
- 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
- Course deviation
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA18IA265
- Event ID
- 20180813X11107
- Case number
- DCA18IA265
- 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: local date, investigation status, cause areas, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2018-08-11.
- API snapshot SHA-256: 575e2dcba8ca5e89edd208ae83741309a1d8b3e382850471670cfba8ed52e1f4; retrieved 2026-09-16T08:04:59.884Z.