37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1377111 |
Time | |
Date | 201608 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | CZYZ.ARTCC |
State Reference | ON |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
While on a base to final vector for runway 23 with toronto approach radio contact with approach was lost. As we were approaching final with I made a radio transmission asking for a vector to join the final. Toronto tower informed me I was on the wrong frequency. I immediately rejoined the approach control frequency. I apologized for my mistake; and approach was able to vector us around for another approach to runway 23. We were at 3;000 feet; speed 200 kts; flaps 20; five or so miles outside of rexdale. I was the pilot monitoring. I knew we would be receiving our final vector to join the inbound course; and I was attempting to be proactive because I was tired. I dialed in the tower frequency; and out of habit I must have moved my finger up to press the button to switch the frequency. Twenty seconds later I realized we needed a vector for final. At that time it was too late; and we had missed valuable radio calls from approach.my technique was terrible. My decision to dial in the frequency at that point in time jeopardized the safety of the entire operation. Instead of saving time I distracted myself. I allowed for an error that went un-trapped at a very critical time. I will never change a frequency in the approach environment unless I am directed to by ATC. As far as I know; there was no conflict created by us flying through final; but in a busy environment like toronto there could have been other aircraft on the opposite downwind leg that could have been put in danger.
Original NASA ASRS Text
Title: CRJ-200 flight crew found themselves on the wrong frequency at short final.
Narrative: While on a base to final vector for runway 23 with Toronto Approach radio contact with approach was lost. As we were approaching final with I made a radio transmission asking for a vector to join the final. Toronto Tower informed me I was on the wrong frequency. I immediately rejoined the approach control frequency. I apologized for my mistake; and approach was able to vector us around for another approach to runway 23. We were at 3;000 feet; speed 200 kts; flaps 20; five or so miles outside of Rexdale. I was the pilot monitoring. I knew we would be receiving our final vector to join the inbound course; and I was attempting to be proactive because I was tired. I dialed in the tower frequency; and out of habit I must have moved my finger up to press the button to switch the frequency. Twenty seconds later I realized we needed a vector for final. At that time it was too late; and we had missed valuable radio calls from approach.My technique was terrible. My decision to dial in the frequency at that point in time jeopardized the safety of the entire operation. Instead of saving time I distracted myself. I allowed for an error that went un-trapped at a very critical time. I will never change a frequency in the approach environment unless I am directed to by ATC. As far as I know; there was no conflict created by us flying through final; but in a busy environment like Toronto there could have been other aircraft on the opposite downwind leg that could have been put in danger.
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.