FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Cargojet Airways Flight 1926

17 Jun 2024 · Milan, IN, United States

Boeing 767-316 ER · Accident: part(s) separation from aircraft en route

From Cincinnati Northern Kentucky International Airport (KCVG) to Vancouver International Airport (CYVR)

Report a problem

Event

NTSB case
DCA24LA210
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
Accident
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
0
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
Airline
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

Boeing 767-316 ER

Aircraft type
Boeing 767
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
C-FCJU
Onboard fatalities
Unknown
Route
From Cincinnati Northern Kentucky International Airport (KCVG), Cincinnati, KYTo Vancouver International Airport (CYVR), Vancouver
Aircraft age
About 28 years (built 1996)
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 129: Foreign
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
En route · cruise
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
Part(s) separation from aircraft
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

On June 17, 2024, Cargojet Airways flight 1926 experienced an in-flight separation of the auxiliary power unit (APU) doors while climbing through 13,000 feet near Milan, Indiana. The flight crew did an air turnback to Cincinnati/Northern Kentucky International Airport (CVG), Hebron, Kentucky, and landed without further incident. Post flight inspection of the airplane revealed that the APU access doors had separated from the airplane and substantially damaged the lower surface of the left and right elevators (see figure 1). The flight was operated under Title 14 Code of Federal Regulations (CFR) Part 129 as a non-scheduled international cargo flight from CVG to Vancouver International Airport (YVR), Vancouver, British Columbia, Canada.

Figure 1. View of the structural damage to the APU doors and elevators. (Source: Cargojet)

The flight was operated by two flight crewmembers that consisted of a captain and a first officer (FO). According to the flight crewmembers, the pre-fight inspection, start-up, taxi, and takeoff were uneventful. There were no unusual noises, vibrations, or Engine Indicating and Crew Alerting System (EICAS) messages observed during the takeoff.

After takeoff, the flight was cleared to FL360 by air traffic control (ATC). While the aircraft was passing through 13,000 feet, the flight crew noted an audible “loud bang” followed by airframe vibrations and a FIRE/OVERHEAT SYS EICAS message. Additionally, the lower EICAS displayed an APU FIRE LOOP 1 and 2 status notification.

The flight crewmembers requested and were instructed by ATC to level off at 17,000 feet and reduce their airspeed to 280 kts. Because the vibrations had stabilized in intensity, they requested a climb to FL240, and they informed dispatch of their situation through the Aircraft Communications Addressing and Reporting System (ACARS). As the flight climbed through FL210, the intensity of the vibrations began to increase, so they levelled off at FL240 and requested to return to CVG. The autopilot remained engaged throughout the flight and the aircraft handled normally. The landing and subsequent taxi to parking was uneventful, with no abnormal noises or vibrations noted. During a postflight inspection of the airplane, the flight crewmembers observed that the APU access doors were missing and the lower surface of the left and right elevators were damaged.

There are two (a left and a right) APU access doors that have four latch assemblies (see Figure 2). The right door contains the latch hooks, and the left door contains the U-bolt and engagement pins. Safety features include a trigger action actuator safety and an overcenter toggle action of the latch handle. The latches are designed so that failure of the spring will not cause the latch to open. The APU access door is opened by pushing the trigger in each latch handle, using moderate thumb pressure, to release the latch safety catch and allow the latch handle and hook to begin the movement required to unlatch the door.

Figure 2. APU doors and latch. (Source: Boeing AMM 52-48-13. Copyright © Boeing. Reproduced with permission.)

Departed sections of the left hand (LH) APU access door were located and recovered. However, the right hand (RH) APU access door, including all four latch hooks, were not recovered. The damaged sections of the LH and RH elevators were removed from the aircraft along with the remaining portions of the LH and RH APU access doors.

The sections of the LH APU access door, a section of the RH APU door, an elevator control rod assembly, an APU door hold open strut, a horizontal stabilizer panel seal, a flexible drive shaft, the LH elevator assembly, and the RH elevator assembly were sent to the Boeing Equipment Quality Analysis (EQA) facility in Seattle, Washington for examination and analysis.

According to Cargojet Airways, their review of the flight data recorder (FDR) data showed that the APU access doors likely began to separate at the onset of the APU fire loop fault indication about 04:56:38Z, at an indicated altitude of 12,011 feet MSL, and an indicated airspeed of about 315 kts. A review of the data also revealed no further anomalies that were related to the occurrence.

Two sections (an aft section and a forward section) of the recovered LH APU door were visually examined at the Boeing EQA. The aft section measured approximately 21 inches along the latch edge and 27 inches along the torn forward edge (see figure 3). The U-bolt, part of the latching mechanism, was visually examined and was unremarkable and typical of an in-service aircraft.

Figure 3. Left photo is of the recovered left hand door aft section and the right photo is a close up of the u-bolt. (Source: Boeing. Photo Copyright © Boeing. Reproduced with permission.)

The forward door section measured approximately 38 inches along the forward edge, and 70 inches along the latch edge. The door was distorted and bent, and the skin was wrinkled in multiple areas (see figure 4). The skin was fractured and bent in the outboard direction at the second support rib from the forward edge of the door. Additionally, the skin was separated from the second support rib with portions of the rivet remaining in the second support rib. The three U-bolts on the forward access door section were visually examined with nothing remarkable.

Figure 4. Recovered left hand door forward section. (Source: Boeing. Photo Copyright © Boeing. Reproduced with permission.)

Cargojet Airways maintenance records showed that during the period of June 15 -17, 2024, the APU oil level was checked as part of a weekly and daily service check. This inspection required the opening and closing of the APU doors. The maintenance technician who conducted the pre-departure check for the accident flight stated that he visually observed the APU doors and that they appeared to be latched and secured.

After the event, Cargojet Airways maintenance conducted a fleet campaign to inspect APU latch assemblies on seventeen (17) B757, three (3) B767-200 and twenty-one (21) B767-300’s. The results of the inspection showed that (3) 757 aircraft and (3) B767-300 aircraft needed adjustments to their latch assemblies to bring them within minimum and maximum closure force limits. For the latch assemblies needing adjustment, maintenance attempted, on the ground in a hangar environment, to simulate vibration and external forces to pull open the door. They were unable to duplicate a failure and open the doors when an out of limit latch was correctly closed.

Because the RH APU access door and latches were not recovered and examined, the exact reason why the APU doors opened in-flight cannot be determined. However, based on the examination of the LH access door, it is likely that one or more latches were not fully engaged and closed before departure.

Probable cause

One or more latches were not fully re-engaged after a service check which resulted in the auxiliary power unit (APU) doors separating from the aircraft during climb out.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA24LA210
Event ID
20240617194480
Case number
DCA24LA210
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: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 2177289d040d31cae0ad5b52956013543d56d112c5890d0c05a9cd445b06d12d; retrieved 2026-09-16T18:54:25.553Z.