37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 376730 |
Time | |
Date | 199708 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : yqx |
State Reference | NF |
Altitude | msl bound lower : 31000 msl bound upper : 31000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : czqx artcc : zdc |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise other |
Route In Use | enroute : atlantic enroute : other oceanic enroute other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : cfi |
Experience | flight time last 90 days : 216 flight time total : 9100 flight time type : 4000 |
ASRS Report | 376730 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | other anomaly other |
Independent Detector | other controllera |
Resolutory Action | other |
Consequence | faa : assigned or threatened penalties Other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | other |
Narrative:
Crossing 52 degrees north, 40 degrees west, I gave a position report to gander radio and included an incorrect fix. Instead of calling the coast in fix as gander VOR, I called cymon. Cymon was on my filed ATC clearance, but gander VOR was on my track message nat 'east.' gander radio called us via SELCAL and asked us to confirm -- gander or cymon? At this time I still thought the coast in fix was cymon, but I started to check because of gander's level of interest. Shortly thereafter gander radio called again and said the fix is gander VOR and that gander center was filing the appropriate report. When I asked what type of report was being filed I was told it was an 'ATC intervention to prevent a gross navigation error.' I have flown many atlantic xings and this is the first time I have ever made this type of error. I contribute, to a large degree, the reason for this situation to fatigue. During this sequence of trips, I have had no schedule to count on and crew staffing is not adequate enough to cover the trips sold.
Original NASA ASRS Text
Title: AS AN ACR WDB FREIGHTER WAS XING THE NORTH ATLANTIC ARTCC CALLED TO ASK ABOUT THE COAST-IN POINT. THE FLC GAVE THE CTLR THE PLANNED POINT, NOT THE ACTUAL POINT AND THEN THE CTLR CORRECTED THEM AND INFORMED THEM THAT A RPT OF A POTENTIAL GROSS NAV ERROR WOULD BE MADE BY ATC.
Narrative: XING 52 DEGS N, 40 DEGS W, I GAVE A POS RPT TO GANDER RADIO AND INCLUDED AN INCORRECT FIX. INSTEAD OF CALLING THE COAST IN FIX AS GANDER VOR, I CALLED CYMON. CYMON WAS ON MY FILED ATC CLRNC, BUT GANDER VOR WAS ON MY TRACK MESSAGE NAT 'E.' GANDER RADIO CALLED US VIA SELCAL AND ASKED US TO CONFIRM -- GANDER OR CYMON? AT THIS TIME I STILL THOUGHT THE COAST IN FIX WAS CYMON, BUT I STARTED TO CHK BECAUSE OF GANDER'S LEVEL OF INTEREST. SHORTLY THEREAFTER GANDER RADIO CALLED AGAIN AND SAID THE FIX IS GANDER VOR AND THAT GANDER CTR WAS FILING THE APPROPRIATE RPT. WHEN I ASKED WHAT TYPE OF RPT WAS BEING FILED I WAS TOLD IT WAS AN 'ATC INTERVENTION TO PREVENT A GROSS NAV ERROR.' I HAVE FLOWN MANY ATLANTIC XINGS AND THIS IS THE FIRST TIME I HAVE EVER MADE THIS TYPE OF ERROR. I CONTRIBUTE, TO A LARGE DEG, THE REASON FOR THIS SIT TO FATIGUE. DURING THIS SEQUENCE OF TRIPS, I HAVE HAD NO SCHEDULE TO COUNT ON AND CREW STAFFING IS NOT ADEQUATE ENOUGH TO COVER THE TRIPS SOLD.
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.