<< >> NASA ASRS Report 649436, March 2005

Flight crew of G200 unable to program a VOR radial track on their FMS; and fail to follow ATC clearance.

Attributes
ACN	649436
Time
Date	200503
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : pbi.vortac
State Reference	FL
Altitude	msl single value : 10000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : pbi.tracon
Operator	general aviation : corporate
Make Model Name	Gulfstream 200 [G200] (IAI 1126 Galaxy)
Operating Under FAR Part	Part 121
Flight Phase	descent : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 68 flight time total : 10200 flight time type : 325
ASRS Report	649436
Person 2
Affiliation	company : corporate
Function	flight crew : first officer
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	other controllerb
Resolutory Action	controller : issued new clearance controller : issued alert
Supplementary
Problem Areas	Flight Crew Human Performance Aircraft
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Pbi approach cleared us to fly on the 092 degree outbound phk; we acknowledged. Myself and sic tried programming FMS to do that. We were not successful; but in the meantime aircraft turned to pbi VOR next fix in FMS and on autoplt. The crew failed to realize that and when I asked sic when we were at 10000 ft over pbi; 'aren't we high for being over airport?' the controller asked 'didn't I ask you to fly the 092 degree outbound phk?' we responded 'yes.' approach control gave us heading; vectors; and descent. Nothing else was said about it. In hindsight; we have switched navigation source from FMS to VOR when we received instructions. Then should have gone back to reprogram FMS. That way if unsuccessful; we would have naved on instructed course information from ATC. Situational awareness should have been higher; and our level of automation lowered to meet the instruction first officer ATC. No conflicts with other aircraft were noted.

Related reports:

• Distracted by the need to program a clearance which is not p...
• MD80 flight crew fail to program required en route transitio...
• Failed to comply with clearance crossing restriction while a...
• A late runway change clearance as the airliner was only a fe...
• MD88 flight crew on novss RNAV SID from atl fails to program...
• Failed to program INS per clearance routing.

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

Original NASA ASRS Text

Title: FLT CREW OF G200 UNABLE TO PROGRAM A VOR RADIAL TRACK ON THEIR FMS; AND FAIL TO FOLLOW ATC CLRNC.

Narrative: PBI APCH CLRED US TO FLY ON THE 092 DEG OUTBOUND PHK; WE ACKNOWLEDGED. MYSELF AND SIC TRIED PROGRAMMING FMS TO DO THAT. WE WERE NOT SUCCESSFUL; BUT IN THE MEANTIME ACFT TURNED TO PBI VOR NEXT FIX IN FMS AND ON AUTOPLT. THE CREW FAILED TO REALIZE THAT AND WHEN I ASKED SIC WHEN WE WERE AT 10000 FT OVER PBI; 'AREN'T WE HIGH FOR BEING OVER ARPT?' THE CTLR ASKED 'DIDN'T I ASK YOU TO FLY THE 092 DEG OUTBOUND PHK?' WE RESPONDED 'YES.' APCH CTL GAVE US HDG; VECTORS; AND DSCNT. NOTHING ELSE WAS SAID ABOUT IT. IN HINDSIGHT; WE HAVE SWITCHED NAV SOURCE FROM FMS TO VOR WHEN WE RECEIVED INSTRUCTIONS. THEN SHOULD HAVE GONE BACK TO REPROGRAM FMS. THAT WAY IF UNSUCCESSFUL; WE WOULD HAVE NAVED ON INSTRUCTED COURSE INFO FROM ATC. SITUATIONAL AWARENESS SHOULD HAVE BEEN HIGHER; AND OUR LEVEL OF AUTOMATION LOWERED TO MEET THE INSTRUCTION FO ATC. NO CONFLICTS WITH OTHER ACFT WERE NOTED.

Data retrieved from NASA's ASRS site as of January 2009 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.