CGAUP
Bell Helicopter Company A Division Of Textron Inc. 206L · built 1976
Register facts: Canadian Civil Aircraft Register (open data, file dated October 27, 2026).
FlightFinder has no observed route profile for this registration. The documented safety events below are available independently of live flight tracking.
Safety history
- April 10, 1993Accident
A FROZEN AILERON CONTROL BEARING AFTER IT HAD BECOME WORN, CORRODED AND EXPOSED TO WATER, AND THE MANUFACTURER'S INADEQUATE MAINTENANCE/INSPECTION REQUIRMENT OF THE BEARING(S). Full accident record
Transportation Safety Board of Canada records12 on file
Worst recorded outcome: minor damage.
- April 3, 2001Incident
A01O0107: The Air Canada Boeing 767-233 aircraft had just departed Kingston Jamaica, (MKJP), on a regularly scheduled flight to Toronto LBPIA. Shortly after departure the flight crew received a message from Kingston that tire debris had been found on the ramp where the aircraft had been parked. As a precaution the…
- September 10, 2000Incident
A00O0197: When the landing gear of the Boeing 767 was selected down for landing the right main landing gear did not indicate that it was down and locked. The flight crew conducted a go-around and requested that ERS stand by for the landing which was uneventful. During the subsequent inspection of the aircraft it was…
- May 27, 2000Incident
A00H0003: A Skyservice Cessna C650 registration C-FJJC was inbound to Montreal Dorval on an IFR flight from Toluca Mexico (MMTO) in descent to 6,000. ACA411, a Boeing B767 (762) registration C-GAUP had departed runway 28 enroute to Toronto via Ottawa on an IFR flight plan and was climbing straight ahead. On initial…
- October 25, 1999Incident
A99O0252: During descent into Toronto the Boeing 767-233 aircraft flight crew increased both engine power settings but the #1 engine (Pratt & Whitney JT9D-7R4) remained at idle. The flight crew declared an emergency advising ATS that they would be landing at Toronto, single engine.On approach after consultation with…
- August 28, 1995Incident
A95o0175: shortly after take-off, heavy smoke appeared in the rear galley of the boeing 767-233 aircraft. The cabin crew discharged a fire extinguisher into the #3 oven and switched off all electrical power to the galley through the utility buses. The smoke dissipated and the air crew requested to return to toronto…
- April 10, 1993Incident
A93o0107: while the boeing 767-233 was cruising at fl 370 enroute from san francisco to toronto,the right autopilot light illuminated. The aircraft was holding altitude, but not following the l/nav path. The aircrew tried the center and left autopilot with the same results, disengaged the systems to manual flight and…
- October 11, 1992Incident
Following the start up of the APU prior to push back from the gate a large cloud of black smoke was reported coming from the APU exhaust. There was no indication in the cockpit of an abnormal APU however the crew shut down the APU and activated the fire bottles. The passengers was were deplaned from the boeing 767…
- May 16, 1989Incident
The aircraft departed from Los Angeles, California on a flight to Toronto, Ontario. At an altitude of 41,000 feet, the aircraft encountered moderate clear air turbulence, and the exhaust gas temperatures (EGT) on both engines (Pratt & Whitney JT9D-7R4D) began to climb and exceed the maximum operating limits. The left…
- August 7, 1987Incidentminor damage
On desc, r/ENG shut down due to low oil pressure. Cfr called out. A/c landed safely. Repl damaged seal at fuel flow transmit.
- May 17, 1987Incident
As the captain of the Boeing 767 began the take-off roll on runway 24R, he observed a Cessna 172 crossing the runway at the runway 10 intersection. The take-off was rejected without further incident. FINDINGS: Cause Related: 1. The ground controller instructed the Cessna 172 pilot to taxi via a routing which crossed…
…and 2 more on file.
Source: TSB Aviation Safety Information System (ASIS) (open data).