<< >> NASA ASRS Report 341723, July 1996

Approach controller working the north arrival sector saw a DC10 encroach on his airspace and get near to his B737 on an ILS to runway 24R. The DC10 was supposed to be on an ILS runway 25L approach but was off course and below the published altitude prior to hunda. Controller got the B737 to accept visual separation after traffic was pointed out and sighted.

Attributes
ACN	341723
Time
Date	199607
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : lax
State Reference	CA
Altitude	msl bound lower : 2500 msl bound upper : 3000
Environment
Flight Conditions	IMC
Light	Dusk
Aircraft 1
Controlling Facilities	tracon : lax
Operator	common carrier : air carrier
Make Model Name	DC-10 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	descent : approach descent other
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
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar
Experience	controller radar : 8
ASRS Report	341723
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	conflict : airborne less severe non adherence : published procedure non adherence : clearance non adherence : required legal separation other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Miss Distance	horizontal : 6000 vertical : 500
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Incident occurred during simultaneous ILS approachs to los angeles. My aircraft was B737 established on runway 24R localizer at 2500 ft. The other aircraft was DC10 established on runway 25L localizer. The DC10 was outside hunda intersection and was supposed to cross it at 3500 ft. The DC10 descended to 3000 ft outside hunda, conflict alert went off and I got the B737 to see the DC10 and maintain visual separation until the parallel monitors took over inside hunda intersection.

Related reports:

• Approach controller observes F15 flight inbound to edf AFB d...
• Boi approach controller reported they had to vector an aircr...
• B737-300 flight crew misses controller instruction to fly ru...
• Flight crew of a cargo flight failed to follow the published...
• LJ55 crew became disoriented on the approach to ILS runway 1...
• Dehavilland DHC8 flight crew advised approach controller out...

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

Original NASA ASRS Text

Title: APCH CTLR WORKING THE N ARR SECTOR SAW A DC10 ENCROACH ON HIS AIRSPACE AND GET NEAR TO HIS B737 ON AN ILS TO RWY 24R. THE DC10 WAS SUPPOSED TO BE ON AN ILS RWY 25L APCH BUT WAS OFF COURSE AND BELOW THE PUBLISHED ALT PRIOR TO HUNDA. CTLR GOT THE B737 TO ACCEPT VISUAL SEPARATION AFTER TFC WAS POINTED OUT AND SIGHTED.

Narrative: INCIDENT OCCURRED DURING SIMULTANEOUS ILS APCHS TO LOS ANGELES. MY ACFT WAS B737 ESTABLISHED ON RWY 24R LOC AT 2500 FT. THE OTHER ACFT WAS DC10 ESTABLISHED ON RWY 25L LOC. THE DC10 WAS OUTSIDE HUNDA INTXN AND WAS SUPPOSED TO CROSS IT AT 3500 FT. THE DC10 DSNDED TO 3000 FT OUTSIDE HUNDA, CONFLICT ALERT WENT OFF AND I GOT THE B737 TO SEE THE DC10 AND MAINTAIN VISUAL SEPARATION UNTIL THE PARALLEL MONITORS TOOK OVER INSIDE HUNDA INTXN.

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.