37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 493216 |
Time | |
Date | 200011 |
Day | Wed |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | navaid : lrp.vortac |
State Reference | PA |
Altitude | msl single value : 15000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zny.artcc |
Operator | common carrier : air carrier |
Make Model Name | De Havilland Canada Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | other vortac |
Flight Phase | cruise : level |
Route In Use | enroute airway : v170.airway |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | artcc : zny.artcc |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | cruise : level |
Route In Use | enroute airway : zzz.airway |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : multi engine pilot : cfi pilot : atp |
Experience | flight time last 90 days : 212 flight time total : 4800 flight time type : 2503 |
ASRS Report | 493216 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument pilot : multi engine |
Experience | flight time last 90 days : 200 flight time total : 3000 flight time type : 620 |
ASRS Report | 493210 |
Events | |
Anomaly | non adherence : clearance non adherence : company policies non adherence : published procedure other spatial deviation |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance |
Consequence | faa : reviewed incident with flight crew other |
Supplementary | |
Problem Areas | Airspace Structure Chart Or Publication Environmental Factor Flight Crew Human Performance ATC Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
We were scheduled to do flight from unv to phl. We departed unv on nov/xa/00. Our route was direct to rashe intersection, V276 rav, V170 to V210 bunts, direct to phl. I was the PF. We took off from unv and contacted ZNY. Center cleared us direct to ravine. We then climbed up to 15000 ft MSL and proceeded on course. The airplane had no RNAV, so I was navigating and using the autoplt. Once at cruise, the first officer and I began a general conversation as I was flying the route. After ravine, I turned outbound on V170 which is the 136 degree radial. There were some communications over the radio, but center did not seem too busy at the time. As we approached bunts intersection, I had not heard a clearance from center and asked the first officer to ask what heading we should head after that intersection. Center proceeded to tell us to turn to a 270 degree heading. The controller, in a very agitated voice, asked us where we had been. He told us we had missed several calls from him. He also told us he had another aircraft try to call us as well as our company. I find it very unusual that the first officer and I each missed several radio calls. Our company also never reached us on our ats call and we were about 35 mi away from our headquarters. Then center asked us what route we were following because we were not on V170. I looked at the en route chart and realized I had missed the turn at boyer intersection. I explained to the controller what had happened, but he did not seem interested. I apologized for the mistake, but he continued to sound very angry as he vectored us around so he could hand us off to phl approach. After landing in phl, the first officer and I discussed what had happened. Neither one of us had heard any calls for us prior to us asking for a heading. We wondered if the controller was using the wrong call sign or flight number and we never caught it. We also realized that we each missed the turn on the route.
Original NASA ASRS Text
Title: A DHC8 FLC FAILS TO FOLLOW THE AIRWAY AS DEPICTED ON THEIR CHART AND ARE UNAWARE OF THE ZNY CTLR'S ATTEMPTS TO CONTACT THEM WHILE OFF THE FILED RTE 13 MI SE OF LRP, PA.
Narrative: WE WERE SCHEDULED TO DO FLT FROM UNV TO PHL. WE DEPARTED UNV ON NOV/XA/00. OUR RTE WAS DIRECT TO RASHE INTXN, V276 RAV, V170 TO V210 BUNTS, DIRECT TO PHL. I WAS THE PF. WE TOOK OFF FROM UNV AND CONTACTED ZNY. CTR CLRED US DIRECT TO RAVINE. WE THEN CLBED UP TO 15000 FT MSL AND PROCEEDED ON COURSE. THE AIRPLANE HAD NO RNAV, SO I WAS NAVING AND USING THE AUTOPLT. ONCE AT CRUISE, THE FO AND I BEGAN A GENERAL CONVERSATION AS I WAS FLYING THE RTE. AFTER RAVINE, I TURNED OUTBOUND ON V170 WHICH IS THE 136 DEG RADIAL. THERE WERE SOME COMS OVER THE RADIO, BUT CTR DID NOT SEEM TOO BUSY AT THE TIME. AS WE APCHED BUNTS INTXN, I HAD NOT HEARD A CLRNC FROM CTR AND ASKED THE FO TO ASK WHAT HDG WE SHOULD HEAD AFTER THAT INTXN. CTR PROCEEDED TO TELL US TO TURN TO A 270 DEG HDG. THE CTLR, IN A VERY AGITATED VOICE, ASKED US WHERE WE HAD BEEN. HE TOLD US WE HAD MISSED SEVERAL CALLS FROM HIM. HE ALSO TOLD US HE HAD ANOTHER ACFT TRY TO CALL US AS WELL AS OUR COMPANY. I FIND IT VERY UNUSUAL THAT THE FO AND I EACH MISSED SEVERAL RADIO CALLS. OUR COMPANY ALSO NEVER REACHED US ON OUR ATS CALL AND WE WERE ABOUT 35 MI AWAY FROM OUR HEADQUARTERS. THEN CTR ASKED US WHAT RTE WE WERE FOLLOWING BECAUSE WE WERE NOT ON V170. I LOOKED AT THE ENRTE CHART AND REALIZED I HAD MISSED THE TURN AT BOYER INTXN. I EXPLAINED TO THE CTLR WHAT HAD HAPPENED, BUT HE DID NOT SEEM INTERESTED. I APOLOGIZED FOR THE MISTAKE, BUT HE CONTINUED TO SOUND VERY ANGRY AS HE VECTORED US AROUND SO HE COULD HAND US OFF TO PHL APCH. AFTER LNDG IN PHL, THE FO AND I DISCUSSED WHAT HAD HAPPENED. NEITHER ONE OF US HAD HEARD ANY CALLS FOR US PRIOR TO US ASKING FOR A HDG. WE WONDERED IF THE CTLR WAS USING THE WRONG CALL SIGN OR FLT NUMBER AND WE NEVER CAUGHT IT. WE ALSO REALIZED THAT WE EACH MISSED THE TURN ON THE RTE.
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.