Boeing 737-300 and Boeing 767-300 incident near New York, New York, July 6, 2008
On July 6, 2008, 2 aircraft, Boeing 737-300 (VPCKW) and Boeing 767-300 (CCCXD), were involved in the same incident near New York, New York (John F. Kennedy Intl airport). No one was hurt; 285 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Air traffic control tower non-compliance with FAA separation requirements for operations on non-intersecting runways where flight paths intersect, and poor judgment by the Local 2 controller in clearing the Boeing 767 for takeoff without accounting for the possibility of a go-around by the Boeing 737.
The probable cause of this incident was JFK air traffic control tower non-compliance with FAA separation requirements for operations on non-intersecting runways where flight paths intersect, and poor judgment by the LC2 controller in clearing LAN533 for takeoff without accounting for the possibility of a go-around by CAY792.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 6, 2008
- Place
- New York, New York · John F. Kennedy Intl · map
- Type
- Incident
- Injuries
- No one was hurt; 285 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft 1
- Boeing 737-300 · all 737-300s on the register
- Registration
- VPCKW · no longer on the register
- Damage
- Not recorded
- Flight
- Flight · foreign airline rules (Part 129)
- Aircraft 2
- Boeing 767-300 · all 767-300s on the register
- Registration
- CCCXD · no longer on the register
- Damage
- Not recorded
- Flight
- Flight · foreign airline rules (Part 129)
The NTSB's narrative for the Boeing 737-300 final · quoted from the NTSB record
Controllers at the John F. Kennedy International Airport tower (JFK ATCT) reported a near midair collision (NMAC) involving Cayman Airways flight 792 (CAY792) and Linea Aerea Nacional de Chile flight 533 (LAN533) near the departure ends of runways 13R and 22L. CAY792 was a Boeing 737-300 that had been cleared to land on runway 22L by the Local 1 controller (LC1) following a flight from Grand Cayman Island to JFK. LAN533 was a Boeing 767-300 that had been cleared for takeoff on runway 13R by the Local 2 controller (LC2) for a flight to Santiago. According to initial reports, CAY792 was executing a missed approach to runway 22L and conflicted with LAN533 as it was departing from runway 13R. Controllers assigned diverging headings to both aircraft to resolve the conflict. According to preliminary radar data, the closest proximity of the two aircraft was slightly over 1/2 mile laterally and 200 feet vertically. At the time of the incident, the weather was VFR with 6 miles visibility and haze.
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 Boeing 767-300 final · quoted from the NTSB record
On July 5, 2008, at 8:36 pm eastern daylight time, an incident reported by controllers as a near midair collision occurred at John F. Kennedy International Airport (JFK), New York, New York involving Cayman Airways flight 792 (CAY792), a Boeing 737-300, and Linea Aerea Nacional de Chile flight 533 (LAN533), a Boeing 767-300. According to initial reports, CAY792 was executing a missed approach to runway 22L and conflicted with LAN533 as it was departing from runway 13R. Controllers assigned diverging headings to both aircraft to resolve the conflict. According to preliminary radar data, the closest proximity of the two aircraft was slightly over 1/2 mile laterally and 200 feet vertically. At the time of the incident, the weather was VFR with 6 miles visibility and haze.
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 Boeing 737-300 from the NTSB's investigation tables, in plain English
What happened, in order
- Air traffic event during approach (IFR missed approach) defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incorrect action selection › ATC personnel
The aircraft
- Landing gear: retractable
- Operator: Cayman Airways LTD
The flight
- Departed from: MWCR Georgetown
- Destination: KJFK New York NY
- Flight plan: IFR
- A second pilot was aboard
Weather at the time
- Wind: from 150° at 6 knots
- Visibility: 6 statute miles
- Sky: broken clouds at 12,000 ft; scat at 800 ft
- Temperature: 72°F (22°C), dew point 66°F (19°C)
- Altimeter: 30.02 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Cabi | 3 | |||
| Flight crew | 2 | |||
| Passengers | 112 |
The factual record for the Boeing 767-300 from the NTSB's investigation tables, in plain English
What happened, in order
- Air traffic event during takeoff defining event
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incorrect action selection › ATC personnel
The aircraft
- Landing gear: retractable
The flight
- Departed from: KJFK New York NY
- Destination: SCEL Santiago
- Flight plan: IFR
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Cabi | 10 | |||
| Flight crew | 2 | |||
| Passengers | 156 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
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.