Ont tower and sct TRACON controllers reported an air carrier was vectored into higher MVA; and nonco...

Attributes
ACN	1704206
Time
Date	201911
Local Time Of Day	1201-1800
Place
Locale Reference	ONT.Airport
State Reference	CA
Aircraft 1
Make Model Name	B737 Next Generation Undifferentiated
Operating Under FAR Part	Part 121
Flight Phase	Landing
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Inflight Event / Encounter CFTT / CFIT

Narrative:

Contra-flow conditions. Aircraft X in position on runway 08L with a flow window. Aircraft Y landing runway 26L. Aircraft Z on a visual approach to runway 26R. Our contra LOA with sct states that we can release an opposite direction departure as long as the departure is 'in the turn' prior to the arrival beginning a ten mile final. I was on the log at ont. The tower controller had aircraft X ready to depart runway 08L with a release window and two arrivals on final. Aircraft Y was close; aircraft Z was 30+ miles to the northeast on an ILS/vis approach to runway 26R. The tower controller took the hand-off on aircraft Z. Visual to runway 26R. When he took the hand-off the tag indicated an ILS approach. At some point the tag changed to a visual approach. He had aircraft Y land runway 26L while aircraft X was in position on runway 08L. He asked aircraft Z to continue on base and told him he would turn him inbound. Aircraft Z continued on base. He cleared aircraft X for immediate take-off as soon as aircraft Y landed. He turned aircraft Z inbound and cleared him to land as aircraft X was turning south. According to aircraft a we had 10.28 miles as aircraft X was turning. Sct filed a report; but I'm not sure what issue the report is reporting. I'm filing this as a record in response to the mor.

Original NASA ASRS Text

Title: ONT Tower and SCT TRACON Controllers reported an air carrier was vectored into higher MVA; and noncompliance with opposite direction operations resulting in an airborne conflict.

Narrative: Contra-flow conditions. Aircraft X in position on Runway 08L with a flow window. Aircraft Y Landing Runway 26L. Aircraft Z on a visual approach to Runway 26R. Our contra LOA with SCT states that we can release an opposite direction departure as long as the departure is 'in the turn' prior to the arrival beginning a ten mile final. I was on the log at ONT. The Tower Controller had Aircraft X ready to depart Runway 08L with a release window and two arrivals on final. Aircraft Y was close; Aircraft Z was 30+ miles to the northeast on an ILS/Vis approach to Runway 26R. The Tower Controller took the hand-off on Aircraft Z. Visual to Runway 26R. When he took the hand-off the tag indicated an ILS approach. At some point the tag changed to a visual approach. He had Aircraft Y land Runway 26L while Aircraft X was in position on Runway 08L. He asked Aircraft Z to continue on base and told him he would turn him inbound. Aircraft Z continued on base. He cleared Aircraft X for immediate take-off as soon as Aircraft Y landed. He turned Aircraft Z inbound and cleared him to land as Aircraft X was turning south. According to Aircraft A we had 10.28 miles as Aircraft X was turning. SCT filed a report; but I'm not sure what issue the report is reporting. I'm filing this as a record in response to the MOR.

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

Ont tower and sct TRACON controllers reported an air carrier was vectored into higher MVA; and noncompliance with opposite direction operations resulting in an airborne conflict.