A BAE3100 making a visual approach into lax, ca, mistakes another aircraft for announced traffic and loses separation with the traffic they were originally instructed to follow.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	398964
Time
Date	199804
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : lax
State Reference	CA
Altitude	msl bound lower : 1900 msl bound upper : 1900
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : lax
Operator	common carrier : air carrier
Make Model Name	Jetstream 31
Operating Under FAR Part	Part 121
Flight Phase	descent : approach
Route In Use	approach : visual enroute : on vectors
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	descent : approach descent other
Route In Use	approach : straight in
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 150 flight time total : 6600 flight time type : 400
ASRS Report	398964
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : airborne less severe non adherence : clearance other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance other
Consequence	Other
Miss Distance	horizontal : 6000 vertical : 300
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Was being vectored to downwind for lax runway 24R visual. Socal pointed out traffic for us to follow at our 2 O'clock, a B737. Captain stated he saw it and to notify approach control. I never saw that traffic. We maneuvered to a right base and then saw a large aircraft approaching from our left. The captain said: 'I wonder who that is?' just then socal issued a panicky- sounding: 'turn right to 360 degrees, climb to 2000 ft.' we were heading about 160 degrees. We then received an uneventful resequence to runway 24R. On final, controller explained that the aircraft we had called in sight was not the one he wanted us to follow (the one we cut off), so he had given us evasive vectors. We had come to the same conclusion just as we were given the evasive vector. The 6 mi visibility didn't help, and it would be safer if both pilots saw and agreed on the identify of an aircraft they will receive a visual approach behind.

Original NASA ASRS Text

Title: A BAE3100 MAKING A VISUAL APCH INTO LAX, CA, MISTAKES ANOTHER ACFT FOR ANNOUNCED TFC AND LOSES SEPARATION WITH THE TFC THEY WERE ORIGINALLY INSTRUCTED TO FOLLOW.

Narrative: WAS BEING VECTORED TO DOWNWIND FOR LAX RWY 24R VISUAL. SOCAL POINTED OUT TFC FOR US TO FOLLOW AT OUR 2 O'CLOCK, A B737. CAPT STATED HE SAW IT AND TO NOTIFY APCH CTL. I NEVER SAW THAT TFC. WE MANEUVERED TO A R BASE AND THEN SAW A LARGE ACFT APCHING FROM OUR L. THE CAPT SAID: 'I WONDER WHO THAT IS?' JUST THEN SOCAL ISSUED A PANICKY- SOUNDING: 'TURN R TO 360 DEGS, CLB TO 2000 FT.' WE WERE HDG ABOUT 160 DEGS. WE THEN RECEIVED AN UNEVENTFUL RESEQUENCE TO RWY 24R. ON FINAL, CTLR EXPLAINED THAT THE ACFT WE HAD CALLED IN SIGHT WAS NOT THE ONE HE WANTED US TO FOLLOW (THE ONE WE CUT OFF), SO HE HAD GIVEN US EVASIVE VECTORS. WE HAD COME TO THE SAME CONCLUSION JUST AS WE WERE GIVEN THE EVASIVE VECTOR. THE 6 MI VISIBILITY DIDN'T HELP, AND IT WOULD BE SAFER IF BOTH PLTS SAW AND AGREED ON THE IDENT OF AN ACFT THEY WILL RECEIVE A VISUAL APCH BEHIND.

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.