Medium large transport flight crew on arrival route, then vectors. Controller then chastised crew for not flying the arrival route. Being off course and proximity of another aircraft. Vectored clear of traffic then assigned ILS approach.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	125348
Time
Date	198910
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : iah
State Reference	TX
Altitude	msl bound lower : 8000 msl bound upper : 8000
Environment
Flight Conditions	Marginal
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : iah
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport
Flight Phase	cruise other descent : approach
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 16000 flight time type : 2200
ASRS Report	125348
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance none taken : insufficient time
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Ambiguous
Air Traffic Incident	other

Narrative:

Operating aus-iah, on the cugar 4 arrival to runway 14L, inside hoagie (iah 305/35 DME) when approach gave us a vector to 090 degree and told us to 'expect runway 26'. About 1 min later, we requested runway 27, controller asked 'who's calling'. We restated call sign and request, and were again told to 'expect 26'. Shortly after, controller began chastising us for not flying the arrival, (to 14L), being off course, and in close proximity to another air carrier and talked about us being confused with his instructions about 'banty' (an arrival course fix) which he never had mentioned. We accepted vectors clear of traffic, later saw traffic, returned to the ILS for runway 14 and landed without incident. Called approach supervisor who advised 'no problem' but had been confused by the controller who had also given him a story about being misunderstood with some sort of 'banty' instructions. No such communication was broadcast. We were simply given an erroneous vector, and then blamed for following instructions. Controller's rate and mode of communication indicated he was overloaded.

Original NASA ASRS Text

Title: MLG FLT CREW ON ARR ROUTE, THEN VECTORS. CTLR THEN CHASTISED CREW FOR NOT FLYING THE ARR ROUTE. BEING OFF COURSE AND PROX OF ANOTHER ACFT. VECTORED CLEAR OF TRAFFIC THEN ASSIGNED ILS APCH.

Narrative: OPERATING AUS-IAH, ON THE CUGAR 4 ARRIVAL TO RWY 14L, INSIDE HOAGIE (IAH 305/35 DME) WHEN APCH GAVE US A VECTOR TO 090 DEG AND TOLD US TO 'EXPECT RWY 26'. ABOUT 1 MIN LATER, WE REQUESTED RWY 27, CTLR ASKED 'WHO'S CALLING'. WE RESTATED CALL SIGN AND REQUEST, AND WERE AGAIN TOLD TO 'EXPECT 26'. SHORTLY AFTER, CTLR BEGAN CHASTISING US FOR NOT FLYING THE ARRIVAL, (TO 14L), BEING OFF COURSE, AND IN CLOSE PROX TO ANOTHER AIR CARRIER AND TALKED ABOUT US BEING CONFUSED WITH HIS INSTRUCTIONS ABOUT 'BANTY' (AN ARRIVAL COURSE FIX) WHICH HE NEVER HAD MENTIONED. WE ACCEPTED VECTORS CLEAR OF TFC, LATER SAW TFC, RETURNED TO THE ILS FOR RWY 14 AND LANDED WITHOUT INCIDENT. CALLED APCH SUPVR WHO ADVISED 'NO PROBLEM' BUT HAD BEEN CONFUSED BY THE CTLR WHO HAD ALSO GIVEN HIM A STORY ABOUT BEING MISUNDERSTOOD WITH SOME SORT OF 'BANTY' INSTRUCTIONS. NO SUCH COM WAS BROADCAST. WE WERE SIMPLY GIVEN AN ERRONEOUS VECTOR, AND THEN BLAMED FOR FOLLOWING INSTRUCTIONS. CTLR'S RATE AND MODE OF COM INDICATED HE WAS OVERLOADED.

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