Gulfstream Aerospace GV SP (G550) and Cessna 750 incident near Ontario, Ca, March 8, 2012
On March 8, 2012 at about 6:42 pm local time, 2 aircraft, Gulfstream Aerospace GV SP (G550) (N128GV) and Cessna 750 (N717XJ), were involved in the same incident near Ontario. The NTSB record does not give the injuries. The weather was conditions the NTSB did not record.
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this incident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 8, 2012 · about 6:42 pm local time · cases in 2012
- Place
- Ontario, Canada
- Type
- Incident
- Injuries
- The NTSB record does not give the injuries.
- Weather
- conditions the NTSB did not record
- Aircraft 1
- Gulfstream Aerospace GV SP (G550) SP G550, built 2012 · all GV SP (G550)s on the register
- Registration
- N128GV · registry record · serial 5363
- Damage
- Not recorded
- Flight
- Business flight · general aviation rules (Part 91)
- Aircraft 2
- Cessna 750 NO SERIES, built 2003 · all 750s on the register
- Registration
- N717XJ · registry record · serial 750-0217
- Damage
- Not recorded
- Flight
- Business flight · general aviation rules (Part 91)
The NTSB's narrative for the Gulfstream Aerospace GV SP (G550) preliminary · quoted from the NTSB record
N217AL, a private Cessna 750, was en route between San Jose, California (KSJC), and Bedford, Massachusetts (KBED) at FL430. N128GV, a private Gulfstream V, was en route between Bradley/Windsor Locks, Connecticut (KBDL), and San Francisco, California (KSFO), at FL430. Twenty nm northwest of YXU VOR on J16 Airway the two aircraft passed, separated by 1 mile laterally and 900 feet vertically, where 5 nm lateral or 2000 foot vertical spacing was required.
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 NTSB's narrative for the Cessna 750 preliminary · quoted from the NTSB record
N217AL, a private Cessna 750, was en route between San Jose, California (KSJC), and Bedford, Massachusetts (KBED) at FL430. N128GV, a private Gulfstream V, was en route between Bradley/Windsor Locks, Connecticut (KBDL), and San Francisco, California (KSFO), at FL430. Twenty nm northwest of YXU VOR on J16 Airway the two aircraft passed, separated by 1 mile laterally and 900 feet vertically, where 5 nm lateral or 2000 foot vertical spacing was required.
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 for the Gulfstream Aerospace GV SP (G550) from the NTSB's investigation tables, in plain English
What happened, in order
- Air traffic event during enroute (cruise) defining event
The NTSB's findings
- cause Personnel issues › Task performance › Communication (personnel) › Accuracy of communication › ATC personnel
- factor Personnel issues › Task performance › Use of equip/info › Use of policy/procedure › ATC personnel
The aircraft
- Landing gear: fixed
- Engine 1: Rolls-Royc BR700-710C411; 0 hours total
- Engine 2: Rolls-Royc BR700-710C411; 0 hours total
The flight
- Departed from: BDL Windsor Locks CT
- Destination: SFO San Francisco CA
- Flight plan: IFR
- A second pilot was aboard
Weather at the time
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
The factual record for the Cessna 750 from the NTSB's investigation tables, in plain English
What happened, in order
- Air traffic event during enroute (cruise) defining event
The NTSB's findings
- cause Personnel issues › Task performance › Communication (personnel) › Accuracy of communication › ATC personnel
- factor Personnel issues › Task performance › Use of equip/info › Use of policy/procedure › ATC personnel
The aircraft
- Landing gear: retractable
The flight
- Departed from: SJC San Jose CA
- Destination: BED Bedford MA
- Flight plan: IFR
- A second pilot was aboard
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.
Connections how this case links to the rest of the register
- N128GV on the register today · the tail number may have moved to another aircraft since
- Gulfstream GV-SP (G550) 406 registered today · the model family and its accident history
- N717XJ on the register today · the tail number may have moved to another aircraft since
- Cessna 750 Citation X 288 registered today · the model family and its accident history
- Cessna 72,677 aircraft on the register
- Engine: Rolls-Royc BR700-710C411 347 aircraft carry this series today · as the NTSB recorded it
- Engine: Rolls-Royc BR700-710C411 347 aircraft carry this series today · as the NTSB recorded it
- Bradley International · departed from
- San Francisco International · bound for
- Mineta San Jose International · departed from
- Laurence G Hanscom Field · bound for
The whole map of how records connect · these connections as data: /graph/accident/OPS12WA430.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
