Track deviation for air carrier large transport flight crew.

Attributes
ACN	200884
Time
Date	199102
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : col
State Reference	NJ
Altitude	msl bound lower : 27000 msl bound upper : 27000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zny
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
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 : first officer
Qualification	other other : other pilot : atp pilot : commercial pilot : flight engineer pilot : instrument
Experience	flight time last 90 days : 240 flight time total : 25000 flight time type : 11000
ASRS Report	200884
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : clearance non adherence : far other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Scheduled flight from newark to bermuda, turned onto omega track 16 mi early. Yelled at by controller for heading into hot warning area given 090 heading away. Joined jfk 150 radial and proceeded uneventfully. First bermuda trip in over a yr. This is a trap that I've seen other people fall into. This is to say that to get on course southeast of jfk from newark you need: a) an ewr STAR over colts neck (does not depict the dixie intersection, B) a low altitude chart to fly the victor airway to prepi intersection, not depicted but shown by extrapolation, C) a jet hi chart to depict owenz intersection and, D) an oceanic chart to get on course. All this within 60 NM of the takeoff airport while trying to confirm and/or update the omega (with no firm outbound navigation fix). The PIC changed kennedy radials from 150 (that I observed and confirmed at last glance across the cockpit) to 166 which he didn't mention. When we were cleared on course, the omega showed a heading of 099 to the outbound fix, but I glanced at the captain's CDI and saw it centered so I ignored the omega. Tuned jfk and the 150 rad and while we were discussing the anomalies, the controller intervened???? I've since customized a natrac work sheet so I can reference all my required navigation data on one piece of paper (less than legal during a linechk, but) simply a matter of a higher than average workload in the northeast corridor with no margin for error.

Original NASA ASRS Text

Title: TRACK DEV FOR ACR LGT FLC.

Narrative: SCHEDULED FLT FROM NEWARK TO BERMUDA, TURNED ONTO OMEGA TRACK 16 MI EARLY. YELLED AT BY CTLR FOR HDG INTO HOT WARNING AREA GIVEN 090 HDG AWAY. JOINED JFK 150 RADIAL AND PROCEEDED UNEVENTFULLY. FIRST BERMUDA TRIP IN OVER A YR. THIS IS A TRAP THAT I'VE SEEN OTHER PEOPLE FALL INTO. THIS IS TO SAY THAT TO GET ON COURSE SE OF JFK FROM NEWARK YOU NEED: A) AN EWR STAR OVER COLTS NECK (DOES NOT DEPICT THE DIXIE INTXN, B) A LOW ALT CHART TO FLY THE VICTOR AIRWAY TO PREPI INTXN, NOT DEPICTED BUT SHOWN BY EXTRAPOLATION, C) A JET HI CHART TO DEPICT OWENZ INTXN AND, D) AN OCEANIC CHART TO GET ON COURSE. ALL THIS WITHIN 60 NM OF THE TKOF ARPT WHILE TRYING TO CONFIRM AND/OR UPDATE THE OMEGA (WITH NO FIRM OUTBOUND NAV FIX). THE PIC CHANGED KENNEDY RADIALS FROM 150 (THAT I OBSERVED AND CONFIRMED AT LAST GLANCE ACROSS THE COCKPIT) TO 166 WHICH HE DIDN'T MENTION. WHEN WE WERE CLRED ON COURSE, THE OMEGA SHOWED A HDG OF 099 TO THE OUTBOUND FIX, BUT I GLANCED AT THE CAPT'S CDI AND SAW IT CTRED SO I IGNORED THE OMEGA. TUNED JFK AND THE 150 RAD AND WHILE WE WERE DISCUSSING THE ANOMALIES, THE CTLR INTERVENED???? I'VE SINCE CUSTOMIZED A NATRAC WORK SHEET SO I CAN REF ALL MY REQUIRED NAV DATA ON ONE PIECE OF PAPER (LESS THAN LEGAL DURING A LINECHK, BUT) SIMPLY A MATTER OF A HIGHER THAN AVERAGE WORKLOAD IN THE NE CORRIDOR WITH NO MARGIN FOR ERROR.

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.