Summary The Ukrainian Cargo Airways Ilyushin 76TD (registration UR-UCT, serial number 0063470089) operating as flight number UKS702 departed Baku, Azerbaijan, destined for Trenton, Ontario, with an intermediate stop at Keflavik, Iceland. As the instrument landing system for Runway24 at Trenton was unserviceable, the aircraft was cleared for the non-directional beacon approach to Runway24. During the approach, the right main landing gear struck a group of trees approximately 70feet high located on the approach centreline, 0.7nautical miles from the runway threshold. The aircraft landed at approximately 0745 eastern daylight time with only minor damage. There were no injuries to the 15crew members. Ce rapport est galement disponible en franais. Other Factual Information The terminal aerodrome forecast (TAF) available to the flight crew prior to departure from Keflavik, Iceland, forecast the weather at Trenton to be: from 0400, wind 3knots, visibility 6statute miles (sm) in mist, sky clear, temporarily from 0400 to 0800 visibility 3sm in mist. Prior to commencing descent into Trenton, the aircraft was in visual meteorological conditions (VMC) with ground features and landmarks in sight. At approximately 07001, the flight crew attempted to obtain the latest weather from the Trenton automatic terminal information service (ATIS). The message on the ATIS frequency stated that all information will be issued by air traffic control (ATC). At approximately 0704, while under control of the Montreal Area Control Centre, the flight crew contacted the Trenton control tower and obtained the latest altimeter setting, confirmed that Runway24 was in use, and that the wind was calm. No other weather information was obtained during this exchange. At approximately 0712, the flight crew decided that a straight-in visual approach to Runway24 would be conducted. A briefing as to aircraft configuration and speed during the approach was completed. While the flight crew independently reviewed the approach plates prior to descent, no approach or missed approach briefing was done. At approximately 0732, Trenton ATC inquired of the flight crew's approach intentions. The flight crew requested and was subsequently cleared for the non-directional beacon (NDB) Runway24 approach. The captain was the pilot flying and was navigating with reference to outside visual cues. The first officer was monitoring the outside references and aircraft instruments. At approximately 0739, the Trenton terminal control unit relayed the following weather information to the flight crew: wind calm, visibility 2sm in mist, and sky clear. Shortly after, the airport was sighted. However, only the furthest portion of Runway24 was visible because the initial portion was obscured by a low layer of fog. The precision approach path indicator (PAPI) lights were visible through the fog layer. The aircraft crossed the Trenton final approach fix (FAF) at 2400feet above sea level (asl), approximately 200feet above the published minimum crossing altitude. At that time, the aircraft was on a descent profile of approximately 3.0degrees to the runway, and established on the inbound track of 241 magnetic (M) (see AppendixA- NDB Runway24 Approach - Vertical Profile and AppendixB- NDB> Runway 24 Approach procedure). At approximately 3.5nautical miles (nm) from the threshold and upon full flap extension, the approach angle of the aircraft increased. At 3.0nm, the aircraft descended below the 3.0degree approach path angle and continued its descent to below the minimum descent altitude (MDA) of 900feet asl (618feet above ground level (agl). At 1.5nm from the runway and at approximately 230 to 260feet agl, the aircraft entered a layer of fog. At approximately one nm from the runway, while in fog, the aircraft descended through a radio height of 89feet agl. Realizing it was low, a verbal call was made and the crew took measures to correct for the low-altitude state. Aircraft pitch was increased from zero to four degrees nose-up and the engine power was increased from 88percent to approximately 90percent. The radio altimeter height continued to decrease until it reached 33feet agl, then it increased to 76feet agl, where it remained constant for the next five seconds. Meanwhile, aircraft heading decreased from 244 M to 239 M, deviating left of the inbound approach course. At approximately 0.75nm from the displaced threshold, the aircraft banked to the right and the heading increased to 251 M. After regaining the inbound approach course, a left bank was performed to realign with the extended runway centreline, after which the aircraft landed. The flight crew was not aware that they had struck trees on the approach. However, during the post-flight aircraft inspection, branches were found on the landing gear. This was not reported to Trenton ATC. Approximately 40minutes after landing, during a routine runway inspection by the Department of National Defence (DND), branches and foliage were found on the runway. Further inspection revealed more branches on the edge of the taxiway where the aircraft was parked and on the right main landing gear. Scrape marks were visible on the fuselage. The occurrence was reported to the TSB by the Directorate of Flight Safety (DFS) of DND. Neither the flight crew nor the company notified the TSB or DFS of the occurrence. According to Ukrainian Cargo Airways (UCA) training procedures, the procedure for a visual approach entails the flight crew using a constant rate of descent from the FAF to the runway. Tables that reference groundspeed, descent rate, distance, and altitude outline the data to be used to obtain the appropriate rate of descent for an approach. UCA procedures state that for descent, approach, and landing, the aircraft shall not descend below a relevant safe altitude, except when permanent visual contact with the ground is established and adequate clearance above all obstacles along the flight path is assured. Also, UCA's definition of a visual approach is a visual flight rules (VFR) approach and landing under direct visibility of landmarks. Runway24 at Trenton is 10000feet long, asphalt covered, and oriented to 243 M. Because its threshold is displaced 1000feet, the landing distance available (LDA) is 9000feet. It is equipped with 3000feet of approach lighting, classified as a short simplified approach light (high intensity) system with runway alignment indicator lights. This incorporates 1600feet of sequenced flashing strobe lights along the centreline of the approach light system. The runway is also equipped with a 3.0-degree PAPI visual glide slope indicator. Aviation routine weather reports (METAR) describe the actual weather conditions at a specified location and time and are taken and issued on the hour. Special weather reports (SPECI) are issued between scheduled METAR transmissions whenever weather conditions fluctuate or are below specified criteria. The METAR and SPECI reports for Trenton from 0600 to 0800 were as follows: 0600 METAR - Wind calm, visibility 4 sm in mist, sky clear, temperature 8C, dew point 7C, altimeter 30.14inches of mercury. 0628 SPECI - Wind calm, visibility 2sm in mist, sky clear. 0633 SPECI - Wind calm, visibility 1sm in mist, sky clear. 0700 METAR - Wind from 050T (T) at 6knots, visibility sm in mist, sky clear, temperature 7C, dew point 7C, altimeter 30.16inches of mercury. 0709 SPECI - Wind from 040T at 3knots, visibility sm in fog, sky clear. 0726 SPECI - Wind from 020T at 3knots, visibility2 sm in mist, sky clear. 0738 SPECI - Winds calm, visibility 5sm in mist, sky clear. 0800 METAR - Wind from 030T at 4knots, visibility 7sm, few clouds at 1000feet, temperature 8C, dew point 8C, altimeter 30.19inches of mercury. The weather information relayed to UKS702 just prior to landing corresponds with the 0726 SPECI report above. It is unknown if the flight crew obtained or was relayed any other weather reports prior to this update. In shallow fog or hazy conditions, entire approach and runway lighting systems may be visible from a considerable distance during the approach. However, this visual reference is likely to diminish rapidly during descent into the fog or haze layer. In some cases, it will reduce the visible length of the approach lights to a very small segment.2 As a flight crew begins its descent through shallow fog, the visibility decreases until nearing the ground. Entering a fog layer can also create the illusion of a pitch-up attitude that may cause a pilot to respond with nose-down correction, which steepens the approach path.3 The operating flight crew during the incident flight consisted of one captain, one first officer, one flight engineer, one navigator, and one radio operator. The captain had approximately 7000total flying hours including approximately 6700 on the IL-76; the first officer had approximately3500 total flying hours including approximately 3000 on the IL-76. Both the captain and the first officer held airline transport pilot licenses (ATPL) issued by the State Administration of Ukraine for Aviation Safety Oversight, with type ratings for the IL-76. Both the first officer and the captain had flown into Trenton previously. The radio operator performed all communications with ATC in English and correctly translated and condensed any ATC clearances into Russian for the remaining crew members, without any apparent difficulty. Two complete flight crews were on board; this is referred to as a double crew in the UCA Operating Manual. The first flight crew operated the aircraft on the Baku to Keflavik leg and the occurrence flight crew operated the aircraft on the Keflavik to Trenton leg. While the occurrence flight crew did not fly the aircraft for the entire portion of the flight, they were on board and accumulating time towards their daily duty period. After the incident, separate resting quarters large enough for all flight crew members were not observed on the aircraft; however, mattresses were observed in the cargo area of the aircraft. The sleep patterns and rest locations of the flight crew during the incident flight could not be ascertained. The aircraft departed Baku at approximately 0000 AZST4 on 04October2007. The occurrence flight crew accumulated approximately 6.4hours of flight time and 17.9hours of total duty time prior to the occurrence. In the preceding two weeks, the flight crew assumed duties on a total of seven flights. The seven flights were operated on the Baku-Trenton-Baku route, which crosses nine time zones. The total duty time accumulated on each flight was similar to the total duty accumulated on the occurrence flight. A rest period was provided for the flight crew after arriving at their destination. The shortest rest period was approximately 25hours, while the longest was approximately 42hours. Prior to the seven flights operated within the two-week period, the captain had 11days off duty, while the remainder of the flight crew had at least 16 days off duty. The following chart outlines the duty hours and rest periods of the occurrence flight crew during the two weeks prior to the occurrence. The daily duty limitations for flight crew members at UCA are 12hours. However, for flights of longer duration, a double crew may be utilized. UCA procedures allow for a 60percent increase of a total duty period for flight crew members operating as double crews. The total allowable duty period may, therefore, be increased to 19.2hours for flight crew members operating in a double-crew context. Prior to any flight duty, UCA procedures require an intact rest period with a duration of not less than the preceding duty period, or 12hours, whichever is greater. In the case of trans-meridian flights5, the duration of the total rest shall be at least 42hours. The flight crew did not receive the required 42-hour rest period after completing five of the six previous flights. Transport Canada regulations regarding flight duty limitations are similar to UCA policy in that a flight can be operated for an extended period of time if provisions are made with respect to flight crew rest and the number of crew members required to operate the flight. The duty period of a flight crew can be extended up to 20hours, provided certain conditions are met. The Transport Canada regulations do not address extra rest after the completion of trans-meridian flights.