Oh, snap!

CADORS 2009C1111:

User Name: Ridley, Rod
Date: 2009/05/11
Further Action Required: Yes
O.P.I.: Aerodrome Safety
Narrative: Whitehorse FIC reported that the drivers of two Air North vehicles positioned a HS 748 onto Taxiway Echo without contacting Whitehorse Radio for authorization.

User Name: Ridley, Rod
Date: 2009/05/13
Further Action Required: No
O.P.I.: System Safety
Narrative: UPDATE Aerodrome Safety reported that Whitehorse airside personnel have had a number of conversations/meetings with the Air North group regarding Air North and their continuing penchant for getting their names up on the CADORS. Both individuals received verbal briefings from the airside /security management. This event had no operational impact.


When no one is looking

I have been reading the CADORS database on a semi-regular basis lately, mostly because I’m a big geek and, um, I’m a big geek — much in the same way that I read the Nuclear Regulatory Commission’s incident summaries. Why? Well, why the hell not?

As with most things in life, it’s better with animals — I get the feeling that CADORS must not have a lot of regular readers:

Aerodrome Safety reported that the airside operations manager at P.A. reports that by the time he received a call from FSS and got airside, the foxy lady was long gone. There have been besides the fox, sightings of a coyote and perhaps a wolf however nothing verified. Resident sharp shooters have tried very long shots at the mammals however without success. Airport personnel continue with twice daily patrols and boundary inspections. This occurrence had no operational impact. (CADORS 2009C1033)

The crew of WJA 418, a WestJet B737, reported a bird strike in the vicinity of the ZZD NDB while on approach to Runway 02 at Edmonton. … Aerodrome Safety reported that the crew of WJA 418 advised that the bird struck the right co-pilot’s window. Although the first officer was startled, there was no damage and the starling sized bird only caused a small impact smear. The aircraft was landed without further incident. (CADORS 2009C1020)

JZA 447, a Jazz CRJ 700, was conducting an ILS approach for Runway 31L at Whitehorse but was required to circle for Runway 13R in order to allow a coyote to be chased off the runway. The aircraft subsequently landed without further incident. … Aerodrome Safety reported that airside operations personnel reported that the varmint may have gotten airside either underneath or over a portion of fencing which is snow packed, however the wily fellow is long gone. There are conflicting reports about the animal’s actual walk about. The coyote may have stayed on the apron and in field and not entered runway 13/31L. (CADORS 2009C0812)

The pilots of two departing aircraft at Medicine Hat observed a coyote on the runway. The coyote exited the runway in both cases as the aircraft approached. … Aerodrome Safety reported that the APM reported that the coyote is long gone. Regular inspections of airport boundaries are done by airside operations personnel. They determine access points and eradication positions. The locating of the varmint’s dens is most difficult. Fortunately for the aviation community Coyote strikes are very rare. This event had no operational impact. (CADORS 2009C0932)

C-GRCX, a Super T Aviation Academy Piper Arrow, was about to depart from Runway 21 at Medicine Hat when the pilot was advised by FSS of a coyote about to enter the runway from the east side. The Arrow’s departure was delayed about 3 minutes. Airport staff were called to chase the coyote away. GLR 7242, a Central Mountain Air Beech 1900, was on the backtrack on Runway 21 for departure to Calgary when the driver of TK 399 called holding short. The coyote spotted TK 399 and ran eastbound from the west infield crossing Runway 21. GLR 7242 was delayed about 4 minutes and C-GRCX was in the circuit and had to modify his circuit due to GLR 7242’s delay. … Aerodrome Safety reported that the APM at Medicine Hat reported that the wily fellow was some 400 yards away from 21/03 and was startled from that position onto the runway. The coyote was chased off the property, however the APM was unable to get a shot at the cagey varmint. As a result of this event two departures were delayed. Airside operations staff continue to do airport boundary inspections. (CADORS 2009C0957)

The crew of TSC 273, an Airbus A-330-200 operated by Air Transat reported hitting a rabbit while arriving at Edmonton International (CYEG). … Aerodrome Safety reported that airside operations personnel recovered and removed the remains of a white tailed Jack Rabbit. The aircraft’s right main gear although somewhat discolored did not suffer any damage; sadly the same cannot be said about the hasenpfeffer. This event had no operational impact. (CADORS 2009C0990)

It’s the same guy writing most of these incident reports. I don’t know what I find stranger — that this stuff has to be tracked and logged in such careful detail, or that there’s a guy out there who likes to be creative in his incident reporting.