Centre Air Canada Airbus Industrie A319-114 incident
Airbus Industrie A319-114 · Incident: system/component malfunction/failure (non-power) during takeoff
From Denver International Airport (DEN) to Toronto Pearson International Airport (CYYZ)
Event
- NTSB case
- DEN08IA123
- 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
- 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
Airbus Industrie A319-114
- Aircraft type
- Airbus A319
- 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-FYJP
- Operator
- Centre Air Canada
- Onboard fatalities
- Unknown
- Route
- From Denver International Airport (DEN), Denver, COTo Toronto Pearson International Airport (CYYZ), Toronto
- Aircraft age
- Not recorded
- 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
- Takeoff
- 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
- System/component malfunction/failure (non-power)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Aircraft › Aircraft systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The first takeoff was rejected because the captain’s side window was not secured. Brake temperatures were allowed to cool below 300 degrees C. before the second takeoff was initiated. After the second takeoff, the gear was left extended to allow the brakes to cool. Retraction was normal. When the flaps were retracted, an F-LOCKED ECAM message illuminated. An emergency was declared and the airplane was configured for landing. Several ECAM messages illuminated, including L/G SYSTEM DISAGREE and L/G NOT DOWN. An uneventful landing was accomplished. Post-incident inspection disclosed the right inboard tire had failed. The tire failure was due to low pressure and the extra heat generated by the first rejected takeoff.
Probable cause
Total failure of the right inboard tire. Contributing to this incident were the low pressure of the tire, and the high tire heat generated by the previous rejected takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN08IA123
- Event ID
- 20080729X01123
- Case number
- DEN08IA123
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2008-07-24.
- API snapshot SHA-256: 5720bcd27e11c0756b2da0109f6d911411d32ded7588c377724988a81459193f; retrieved 2026-09-15T09:57:32.016Z.