Narrative:

Aircraft #1 landing hnd runway 17R; aircraft #2 departure runway 19R at las. Controller was under the misconception that hnd class D airspace was procedurally separated from las IFR departures. Also it was thought that once an IFR aircraft enters class D airspace; the tower is responsible to ensure that the aircraft stays inside class D airspace. Aircraft #1 was on a right base to runway 17R at hnd and widened out before turning base; where it came into close proximity to aircraft #2 departure las. Management's solution to the problem was to instruct the controller to use a left base to runway 17R and to coordination that with the hnd tower since it is opposite their normal traffic pattern. However; this does not do any more to ensure separation with runway 19 departures at las because a short centerline extension point from runway 17R at hnd is barely 3 NM from the first waypoints off of runway 19 at las. This has brought up subsequent questions about legal separation between IFR departures and arrs into hnd from sector boundaries; adjacent facility airspace; and IFR departures off of las. Clearly; procedures at this airport which is only 6 NM from las need to be established as it is with other satellite airports. But to this date management refuses to establish any procedures or provide any guidelines which would ensure legal separation due to noise sensitive areas.

Related reports:

Google
 

Original NASA ASRS Text

Title: L30 CTLR EXPERIENCED OPERROR AT 3500 FT WHEN MISJUDGING SEPARATION BTWN HND ARR VERSUS LAS DEP.

Narrative: ACFT #1 LNDG HND RWY 17R; ACFT #2 DEP RWY 19R AT LAS. CTLR WAS UNDER THE MISCONCEPTION THAT HND CLASS D AIRSPACE WAS PROCEDURALLY SEPARATED FROM LAS IFR DEPS. ALSO IT WAS THOUGHT THAT ONCE AN IFR ACFT ENTERS CLASS D AIRSPACE; THE TWR IS RESPONSIBLE TO ENSURE THAT THE ACFT STAYS INSIDE CLASS D AIRSPACE. ACFT #1 WAS ON A R BASE TO RWY 17R AT HND AND WIDENED OUT BEFORE TURNING BASE; WHERE IT CAME INTO CLOSE PROX TO ACFT #2 DEP LAS. MGMNT'S SOLUTION TO THE PROB WAS TO INSTRUCT THE CTLR TO USE A L BASE TO RWY 17R AND TO COORD THAT WITH THE HND TWR SINCE IT IS OPPOSITE THEIR NORMAL TFC PATTERN. HOWEVER; THIS DOES NOT DO ANY MORE TO ENSURE SEPARATION WITH RWY 19 DEPS AT LAS BECAUSE A SHORT CTRLINE EXTENSION POINT FROM RWY 17R AT HND IS BARELY 3 NM FROM THE FIRST WAYPOINTS OFF OF RWY 19 AT LAS. THIS HAS BROUGHT UP SUBSEQUENT QUESTIONS ABOUT LEGAL SEPARATION BTWN IFR DEPS AND ARRS INTO HND FROM SECTOR BOUNDARIES; ADJACENT FACILITY AIRSPACE; AND IFR DEPS OFF OF LAS. CLRLY; PROCS AT THIS ARPT WHICH IS ONLY 6 NM FROM LAS NEED TO BE ESTABLISHED AS IT IS WITH OTHER SATELLITE ARPTS. BUT TO THIS DATE MGMNT REFUSES TO ESTABLISH ANY PROCS OR PROVIDE ANY GUIDELINES WHICH WOULD ENSURE LEGAL SEPARATION DUE TO NOISE SENSITIVE AREAS.

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.