<< >> NASA ASRS Report 545976, May 2002

A heading track deviation occurs in a g-iii when the crew programs the landing runway into the computer, deleting the transition to barin intersection near iad, va.

Attributes
ACN	545976
Time
Date	200205
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	intersection : falko
State Reference	VA
Altitude	msl single value : 10000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : iad.tracon
Operator	general aviation : corporate
Make Model Name	Gulfstream III
Operating Under FAR Part	Part 91
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	arrival star : coatt 4
Flight Plan	IFR
Person 1
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 60 flight time total : 14000 flight time type : 6000
ASRS Report	545976
Person 2
Affiliation	company : corporate
Function	flight crew : first officer
Events
Anomaly	non adherence : published procedure non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued advisory controller : issued new clearance flight crew : returned to intended or assigned course flight crew : became reoriented other
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Company Flight Crew Human Performance Aircraft
Primary Problem	Aircraft
Air Traffic Incident	Pilot Deviation

Narrative:

Iad was landing runway 19L, runway 19R and runway 12. Late confirmation of the landing runway (runway 19R) involved programming the FMS with the ILS approach while nearing brooke. Once the FMS was programmed, it deleted the transition to barin. The aircraft reverted to heading and continued on a 034 degree heading with no warnings displayed. Approach asked if we were going to barin. We were given a vector back on course. I normally fly on giv's and gv's that have honeywell FMS's. This giii has a different kind of FMS. I am used to an FMS that FMS reverts to heading and displays a message 'couple data invalid' appear. On the other FMS, it just keeps on truckin' on the last coupled course. No excuse -- bad situational awareness coupled with minimal FMS knowledge brews trouble.

Related reports:

• Altitude deviation altitude excursion from assigned. Flight ...
• A B737-300 flight crew on the civet 5 arrival to lax got a l...
• Confusion reigned at mem when an A300 flight crew crossed lt...
• An emb-170 flight crew inbound to dfw filed for; set up and ...
• The reporter departed fll runway 9R and was vectored to the ...

	Enter your search terms Submit search form
	Web www.37000feet.com

Original NASA ASRS Text

Title: A HDG TRACK DEV OCCURS IN A G-III WHEN THE CREW PROGRAMS THE LNDG RWY INTO THE COMPUTER, DELETING THE TRANSITION TO BARIN INTXN NEAR IAD, VA.

Narrative: IAD WAS LNDG RWY 19L, RWY 19R AND RWY 12. LATE CONFIRMATION OF THE LNDG RWY (RWY 19R) INVOLVED PROGRAMMING THE FMS WITH THE ILS APCH WHILE NEARING BROOKE. ONCE THE FMS WAS PROGRAMMED, IT DELETED THE TRANSITION TO BARIN. THE ACFT REVERTED TO HDG AND CONTINUED ON A 034 DEG HDG WITH NO WARNINGS DISPLAYED. APCH ASKED IF WE WERE GOING TO BARIN. WE WERE GIVEN A VECTOR BACK ON COURSE. I NORMALLY FLY ON GIV'S AND GV'S THAT HAVE HONEYWELL FMS'S. THIS GIII HAS A DIFFERENT KIND OF FMS. I AM USED TO AN FMS THAT FMS REVERTS TO HDG AND DISPLAYS A MESSAGE 'COUPLE DATA INVALID' APPEAR. ON THE OTHER FMS, IT JUST KEEPS ON TRUCKIN' ON THE LAST COUPLED COURSE. NO EXCUSE -- BAD SITUATIONAL AWARENESS COUPLED WITH MINIMAL FMS KNOWLEDGE BREWS TROUBLE.

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.