37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 379354 |
Time | |
Date | 199709 |
Day | Mon |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : mht |
State Reference | NH |
Altitude | msl bound lower : 10000 msl bound upper : 10000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : intermediate altitude |
Route In Use | enroute : on vectors enroute airway : zbw |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : commercial |
Experience | flight time last 90 days : 200 flight time total : 6800 flight time type : 800 |
ASRS Report | 379354 |
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 | other controllera |
Resolutory Action | other |
Consequence | Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were climbing to our assigned altitude of 16000 ft. We had been given a heading of 300 degrees and told to proceed direct to cambridge VOR when receiving. We mistakenly had chester VOR tuned in, instead of cambridge. We began to proceed to chester which was about 30 degrees south of our course. Approximately 5 mins later, we were told to turn right to a heading of 320 degrees and switch to another controller. It was at this time we realized our error. The new controller said this was a vector around holding traffic. We continued our climb and eventually was cleared again to cambridge VOR. Nothing else was said by us or the controller regarding this event. I do not believe there was any conflict. This event I believe was caused by complacency, and the fact that the 2 vors have very similar frequencys.
Original NASA ASRS Text
Title: FLC OF AN ACR TURBOPROP TUNED IN THE WRONG VOR AND HEADED FOR IT INSTEAD OF THE VOR GIVEN BY ATC. ATC INTERVENED AND VECTORED THEM BACK ON COURSE.
Narrative: WE WERE CLBING TO OUR ASSIGNED ALT OF 16000 FT. WE HAD BEEN GIVEN A HDG OF 300 DEGS AND TOLD TO PROCEED DIRECT TO CAMBRIDGE VOR WHEN RECEIVING. WE MISTAKENLY HAD CHESTER VOR TUNED IN, INSTEAD OF CAMBRIDGE. WE BEGAN TO PROCEED TO CHESTER WHICH WAS ABOUT 30 DEGS S OF OUR COURSE. APPROX 5 MINS LATER, WE WERE TOLD TO TURN R TO A HDG OF 320 DEGS AND SWITCH TO ANOTHER CTLR. IT WAS AT THIS TIME WE REALIZED OUR ERROR. THE NEW CTLR SAID THIS WAS A VECTOR AROUND HOLDING TFC. WE CONTINUED OUR CLB AND EVENTUALLY WAS CLRED AGAIN TO CAMBRIDGE VOR. NOTHING ELSE WAS SAID BY US OR THE CTLR REGARDING THIS EVENT. I DO NOT BELIEVE THERE WAS ANY CONFLICT. THIS EVENT I BELIEVE WAS CAUSED BY COMPLACENCY, AND THE FACT THAT THE 2 VORS HAVE VERY SIMILAR FREQS.
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.