The U.S. aircraft register, updated daily
Accidents · NTSB DCA27WA018 · Preliminary: the investigation is not finished

Boeing 767 incident near Chalhuanca, Outside the U.S., October 16, 2026

On October 16, 2026 at about 3:30 pm local time, a 2007 Boeing 767, registered CCCWV, was involved in an incident during enroute (cruise) near Chalhuanca, Outside the U.S.. It was flown under non-U.S. commercial rules. No one was hurt; 208 people were on board or involved.

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
October 16, 2026 · about 3:30 pm local time · cases in 2026
Place
Chalhuanca, Peru · map
Type
Incident
Injuries
No one was hurt; 208 people were on board or involved.
Weather
not recorded
Aircraft
Boeing 767 316, built 2007 · all 767s on the register
Registration
CCCWV · registered outside the United States · serial 35230
Damage
Not recorded
Flight
Flight · non-U.S. commercial rules

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Pressure/environ sys malf/fail during enroute (cruise) defining event

The aircraft

  • Landing gear: retractable
  • Engine 1: Ge CF6-80C2B7F (turbofan); 0 hours total
  • Engine 2: Ge CF6-80C2B7F (turbofan); 0 hours total

The flight

  • Departed from: SPJC Lima
  • Destination: SBGR Sao Paulo
  • A second pilot was aboard

Weather at the time

  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Cabi5
Flight crew2
Passengers201

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

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/DCA27WA018.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.