 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Reporter implies less than standard separation between C172 on approach to hhr and a B737 on vector to lax runway 24R when aircraft were separated by 300 ft and less than 3 mi.
| Attributes | |
| ACN | 377385 |
| Time | |
| Date | 199708 |
| Day | Sun |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : hhr airport : lax |
| State Reference | CA |
| Altitude | msl bound lower : 2200 msl bound upper : 2500 |
| Environment | |
| Flight Conditions | Marginal |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : lax |
| Operator | general aviation : personal |
| Make Model Name | Skyhawk 172/Cutlass 172 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | descent : approach |
| Route In Use | approach : straight in arrival 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 | cruise other descent : approach |
| Route In Use | arrival other enroute : on vectors |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | other personnel other |
| Qualification | controller : radar |
| Experience | controller military : 3 controller radar : 13 |
| ASRS Report | 377385 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : approach |
| Qualification | controller : radar |
| Events | |
| Anomaly | conflict : airborne less severe other anomaly other |
| Independent Detector | other other : unspecified other other : unspecified atc |
| Resolutory Action | none taken : unable none taken : anomaly accepted |
| Consequence | Other |
| Miss Distance | horizontal : 16800 vertical : 300 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | other |
Narrative:
The C172 was on a straight-in approach to hhr on the runway 25 localizer at 2200 ft, outside of hashy. The B737 was on a vector to runway 24R into lax at 2500 ft. They were separated by 300 ft and less than 3 mi. I observed this situation from the parallel monitor position. The incident was reported to the supervisor, who advised me that the waiver on file makes this legal. I beg to differ. Callback conversation with reporter revealed the following information: reporter stated the waiver was for traffic on approach to hhr from the OM simultaneous with traffic on a vector approach for runway 24R. Reporter said the waiver has been changed to include the final approach course beyond the OM to hashy intersection. Reporter indicated the reported incident was not an operational error as the lateral separation was within the 1/8 mi criteria for the ARTS log tracking printout of the aircraft involved.
Original NASA ASRS Text
Title: RPTR IMPLIES LTSS BTWN C172 ON APCH TO HHR AND A B737 ON VECTOR TO LAX RWY 24R WHEN ACFT WERE SEPARATED BY 300 FT AND LESS THAN 3 MI.
Narrative: THE C172 WAS ON A STRAIGHT-IN APCH TO HHR ON THE RWY 25 LOC AT 2200 FT, OUTSIDE OF HASHY. THE B737 WAS ON A VECTOR TO RWY 24R INTO LAX AT 2500 FT. THEY WERE SEPARATED BY 300 FT AND LESS THAN 3 MI. I OBSERVED THIS SIT FROM THE PARALLEL MONITOR POS. THE INCIDENT WAS RPTED TO THE SUPVR, WHO ADVISED ME THAT THE WAIVER ON FILE MAKES THIS LEGAL. I BEG TO DIFFER. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THE WAIVER WAS FOR TFC ON APCH TO HHR FROM THE OM SIMULTANEOUS WITH TFC ON A VECTOR APCH FOR RWY 24R. RPTR SAID THE WAIVER HAS BEEN CHANGED TO INCLUDE THE FINAL APCH COURSE BEYOND THE OM TO HASHY INTXN. RPTR INDICATED THE RPTED INCIDENT WAS NOT AN OPERROR AS THE LATERAL SEPARATION WAS WITHIN THE 1/8 MI CRITERIA FOR THE ARTS LOG TRACKING PRINTOUT OF THE ACFT INVOLVED.
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.