B737-300 crew had a track deviation departing las on an RNAV departure. The aircraft turned toward a fix not intended by the crew. The aircraft is only equipped with a single FMS, and has no navigation display.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	594245
Time
Date	200309
Day	Wed
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : las.airport
State Reference	NV
Altitude	agl bound lower : 500 agl bound upper : 1000
Environment
Light	Night
Aircraft 1
Controlling Facilities	tracon : l30.tracon
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	climbout : initial climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 700 flight time total : 25000 flight time type : 20000
ASRS Report	594245
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : clearance non adherence : far non adherence : published procedure other spatial deviation
Independent Detector	atc equipment other atc equipment : radar other controllera
Resolutory Action	controller : issued new clearance controller : issued alert
Supplementary
Problem Areas	Flight Crew Human Performance FAA Aircraft Company
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

RNAV departure off runway 7L at las. Per procedures, hand flown with flight director to 400 ft AGL then autoplt. When autoplt engaged, aircraft turned right, away from fix. Disengaged just as departure asked about our heading and gave us a vector. Fixes in 'box' were correct -- runway, fix, departure procedure, etc. Strong crosswind from left, but aircraft corrected more to right, off course rather than left into wind. When asked, first officer gave wrong first fix to controller (not the one in the RNAV), but eventually got that straight that we had programmed it right, but aircraft went off. We seemed to be headed towards a fix for the runway 7R departure, but box said runway 7L, until I disengaged and corrected. Controller stated that it was 'no problem' and we continued uneventfully using the RNAV for the rest of the departure. Aircraft does not have navigation display of course, fixes, etc, as does newer model. So hard to keep tabs on position with vors tuning for the RNAV and giving no useful information.

Original NASA ASRS Text

Title: B737-300 CREW HAD A TRACK DEV DEPARTING LAS ON AN RNAV DEP. THE ACFT TURNED TOWARD A FIX NOT INTENDED BY THE CREW. THE ACFT IS ONLY EQUIPPED WITH A SINGLE FMS, AND HAS NO NAV DISPLAY.

Narrative: RNAV DEP OFF RWY 7L AT LAS. PER PROCS, HAND FLOWN WITH FLT DIRECTOR TO 400 FT AGL THEN AUTOPLT. WHEN AUTOPLT ENGAGED, ACFT TURNED R, AWAY FROM FIX. DISENGAGED JUST AS DEP ASKED ABOUT OUR HDG AND GAVE US A VECTOR. FIXES IN 'BOX' WERE CORRECT -- RWY, FIX, DEP PROC, ETC. STRONG XWIND FROM L, BUT ACFT CORRECTED MORE TO R, OFF COURSE RATHER THAN L INTO WIND. WHEN ASKED, FO GAVE WRONG FIRST FIX TO CTLR (NOT THE ONE IN THE RNAV), BUT EVENTUALLY GOT THAT STRAIGHT THAT WE HAD PROGRAMMED IT RIGHT, BUT ACFT WENT OFF. WE SEEMED TO BE HEADED TOWARDS A FIX FOR THE RWY 7R DEP, BUT BOX SAID RWY 7L, UNTIL I DISENGAGED AND CORRECTED. CTLR STATED THAT IT WAS 'NO PROB' AND WE CONTINUED UNEVENTFULLY USING THE RNAV FOR THE REST OF THE DEP. ACFT DOES NOT HAVE NAV DISPLAY OF COURSE, FIXES, ETC, AS DOES NEWER MODEL. SO HARD TO KEEP TABS ON POS WITH VORS TUNING FOR THE RNAV AND GIVING NO USEFUL INFO.

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.