DC9-30 heading track deviation near ptw.

Attributes
ACN	458680
Time
Date	199912
Day	Wed
Local Time Of Day	1801 To 2400
Place
State Reference	PA
Altitude	msl single value : 31000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zdc.artcc
Operator	common carrier : air carrier
Make Model Name	DC-9 30
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Route In Use	enroute airway : j48.airway
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial pilot : cfi pilot : atp pilot : multi engine
Experience	flight time last 90 days : 240 flight time total : 5500 flight time type : 1200
ASRS Report	458680
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : far non adherence : clearance other spatial deviation
Independent Detector	other flight crewa other flight crewb
Resolutory Action	flight crew : returned to intended or assigned course flight crew : returned to original clearance
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Between 2 navaids -- pottstown and westminster at the cop (J48), captain (PF) switched navigation select to navigation #2 -- the proper inbound frequency and radial. Flight attendant then entered cockpit. Captain switched to navigation #1 and continued flying. By not having selected the correct navigation radio, we deviated from course by a few mi. Factors involved were the distraction of the flight attendant. A large factor was that among our 40 DC9 aircraft there are 3 different navigation setups. We were flying in one that is different from the norm. Corrective action was taken by selecting the correct navigation and flight was continued uneventfully. The deviation was discovered when ATC asked about our position. I believe a company wide standard cockpit layout would have helped avoid a problem like this.

Original NASA ASRS Text

Title: DC9-30 HDG TRACK DEV NEAR PTW.

Narrative: BTWN 2 NAVAIDS -- POTTSTOWN AND WESTMINSTER AT THE COP (J48), CAPT (PF) SWITCHED NAV SELECT TO NAV #2 -- THE PROPER INBOUND FREQ AND RADIAL. FLT ATTENDANT THEN ENTERED COCKPIT. CAPT SWITCHED TO NAV #1 AND CONTINUED FLYING. BY NOT HAVING SELECTED THE CORRECT NAV RADIO, WE DEVIATED FROM COURSE BY A FEW MI. FACTORS INVOLVED WERE THE DISTR OF THE FLT ATTENDANT. A LARGE FACTOR WAS THAT AMONG OUR 40 DC9 ACFT THERE ARE 3 DIFFERENT NAV SETUPS. WE WERE FLYING IN ONE THAT IS DIFFERENT FROM THE NORM. CORRECTIVE ACTION WAS TAKEN BY SELECTING THE CORRECT NAV AND FLT WAS CONTINUED UNEVENTFULLY. THE DEV WAS DISCOVERED WHEN ATC ASKED ABOUT OUR POS. I BELIEVE A COMPANY WIDE STANDARD COCKPIT LAYOUT WOULD HAVE HELPED AVOID A PROB LIKE THIS.

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.