37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 242070 |
Time | |
Date | 199305 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : cmh |
State Reference | ID |
Altitude | msl bound lower : 20000 msl bound upper : 28000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zid |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport |
Navigation In Use | Other |
Flight Phase | climbout : intermediate altitude |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 180 flight time total : 5000 flight time type : 180 |
ASRS Report | 242070 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | non adherence : clearance other anomaly other other spatial deviation |
Independent Detector | atc equipment other atc equipment : unspecified other controllera |
Resolutory Action | controller : issued new clearance other |
Consequence | Other |
Supplementary | |
Primary Problem | Navigational Facility |
Air Traffic Incident | Pilot Deviation other |
Situations | |
ATC Facility | procedure or policy : unspecified |
Narrative:
During climb out from cmh to bna, we were given direct lexington, frequency 112.6, by ZID. Our altitude was FL200 climbing to FL350. Center questioned our initial heading, then turned us approximately 90 degrees to the right for lexington. We tuned the proper frequency previously, idented hyk (although weak and scratchy), but our needles initially pointed to clarksburg VOR, also frequency 112.6. It wasn't until reaching approximately FL280 climbing to FL350 did we receive hyk (lexington) suitable for navigation. ATC was aware of the possibility of confusion. The controller knew the distance between the navaids and was aware this separation could pose a problem for navigation, particularly at lower altitudes. It seems a frequency change is in order for one of the vors. If not possible, ATC should not give 'direct' instructions when the possibility of tracking to the wrong VOR exists.
Original NASA ASRS Text
Title: FLC OF MLG ACR ACFT DEVIATED FROM ASSIGNED TRACK DURING A DIRECT CLB TO HIGH ALT DUE TO THE SAME VORTAC FREQ RECEIVED BY THE ACFT'S RECEIVER.
Narrative: DURING CLBOUT FROM CMH TO BNA, WE WERE GIVEN DIRECT LEXINGTON, FREQ 112.6, BY ZID. OUR ALT WAS FL200 CLBING TO FL350. CTR QUESTIONED OUR INITIAL HDG, THEN TURNED US APPROX 90 DEGS TO THE R FOR LEXINGTON. WE TUNED THE PROPER FREQ PREVIOUSLY, IDENTED HYK (ALTHOUGH WEAK AND SCRATCHY), BUT OUR NEEDLES INITIALLY POINTED TO CLARKSBURG VOR, ALSO FREQ 112.6. IT WASN'T UNTIL REACHING APPROX FL280 CLBING TO FL350 DID WE RECEIVE HYK (LEXINGTON) SUITABLE FOR NAV. ATC WAS AWARE OF THE POSSIBILITY OF CONFUSION. THE CTLR KNEW THE DISTANCE BTWN THE NAVAIDS AND WAS AWARE THIS SEPARATION COULD POSE A PROB FOR NAV, PARTICULARLY AT LOWER ALTS. IT SEEMS A FREQ CHANGE IS IN ORDER FOR ONE OF THE VORS. IF NOT POSSIBLE, ATC SHOULD NOT GIVE 'DIRECT' INSTRUCTIONS WHEN THE POSSIBILITY OF TRACKING TO THE WRONG VOR EXISTS.
Data retrieved from NASA's ASRS site as of July 2007 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.