37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1145932 |
Time | |
Date | 201401 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | CYUL.TRACON |
State Reference | PQ |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR HABBS 3 |
Flight Plan | IFR |
Component | |
Aircraft Component | Aero Charts |
Person 1 | |
Function | Pilot Flying First Officer |
Person 2 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Upon contact with montreal arrival; whilst on the HABBS3 arrival (jepp 10-2B); we were assigned runway 24R and read it back. The approach was loaded and briefed. The transition for [runway] 24R was entered in the FMS. After tidas intersection the FMS made a smart turn toward omeki; between tidas and lonna as it was depicted on the FMS. ATC queried 'air carrier X; turn heading 060; you were supposed to remain on previous heading.' ATC did not assign any heading at all and we were in LNAV. Cyul jepp 10-2B doesn't display any heading post of tidas intersection. Nothing is mentioned of a heading to continue on. On that very same chart at rudsu intersection it shows arrows and a clearly depicted numeric heading value. At tidas intersection; it only shows arrows with no numeric heading depiction. ATC did not assign a heading; only runway 24R transition. The chart has a discrepancy on it as I have indicated above. ATC communication and complication errors are what in my opinion caused this. To add to the complications; ATC were communicating mostly in french with other aircraft; considering ICAO is headquartered in montreal and there's an ICAO requirement to have ICAO aviation english proficiency for air carriers; ATC is to blame for the lack of situational awareness it exerts by communicating in anything other than english. We and one other out of dozens; were the only aircraft he was talking english to at that time.jepp 10-2B needs to be revised with a heading value after tidas. Exactly one day after this event; I flew to cyyc. I noticed on chart 10-2E for cyyc; that in the top right corner of the chart it shows a sort of 'legend' in a box; defining the meaning of the arrows that were present also on chart 10-2B for cyul. A mere comparison of these two charts at these two airports; clearly in my opinion exerts errors on jeppesen's behalf; as the chart 10-2B for cyul needs to have the same definition/instructions for the arrows either as shown in the lower part of cyul 10-2B or as clearly defined in cyyc 10-2E. Cami was used in this case; however the instruction was contradicting and with ATC congesting the frequency in french; it was almost impossible to get a word in until he contacted us again. Montreal ATC needs to comply with ICAO english proficiency requirements. Perhaps in french they gave everyone else the 060 heading; they certainly did not give us any heading instruction in english; the only instruction we received was 'XXXX; runway 24R transition.'
Original NASA ASRS Text
Title: An aircraft on the CYUL HABBS THREE arrival for Runway 24R with LNAV engage; turned toward OMEKI Intersection on the ILS after passing TIDAS but ATC reassigned a 060 heading and advised they should have maintained 060 after TIDAS. The crew contended the chart should have specified the heading.
Narrative: Upon contact with Montreal Arrival; whilst on the HABBS3 Arrival (Jepp 10-2B); we were assigned Runway 24R and read it back. The approach was loaded and briefed. The transition for [Runway] 24R was entered in the FMS. After TIDAS Intersection the FMS made a smart turn toward OMEKI; between TIDAS and LONNA as it was depicted on the FMS. ATC Queried 'ACR X; Turn heading 060; you were supposed to remain on previous heading.' ATC did not assign any heading at all and we were in LNAV. CYUL Jepp 10-2B doesn't display any heading post of TIDAS Intersection. Nothing is mentioned of a heading to continue on. On that very same chart at RUDSU Intersection it shows arrows and a clearly depicted numeric heading value. At TIDAS Intersection; it only shows arrows with no numeric heading depiction. ATC did not assign a heading; only Runway 24R transition. The chart has a discrepancy on it as I have indicated above. ATC communication and complication errors are what in my opinion caused this. To add to the complications; ATC were communicating mostly in French with other aircraft; considering ICAO is headquartered in Montreal and there's an ICAO requirement to have ICAO aviation English proficiency for air carriers; ATC is to blame for the lack of situational awareness it exerts by communicating in anything other than English. We and one other out of dozens; were the only aircraft he was talking English to at that time.Jepp 10-2B needs to be revised with a heading value after TIDAS. Exactly one day after this event; I flew to CYYC. I noticed on Chart 10-2E for CYYC; that in the top right corner of the chart it shows a sort of 'legend' in a box; defining the meaning of the arrows that were present also on chart 10-2B for CYUL. A mere comparison of these two charts at these two airports; clearly in my opinion exerts errors on Jeppesen's behalf; as the chart 10-2B for CYUL needs to have the same definition/instructions for the arrows either as shown in the lower part of CYUL 10-2B or as clearly defined in CYYC 10-2E. CAMI was used in this case; however the instruction was contradicting and with ATC congesting the frequency in French; it was almost impossible to get a word in until he contacted us again. Montreal ATC needs to comply with ICAO English Proficiency requirements. Perhaps in French they gave everyone else the 060 heading; they certainly did not give us any heading instruction in English; the only instruction we received was 'XXXX; Runway 24R Transition.'
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.