37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 995988 |
Time | |
Date | 201202 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | LAX.Airport |
State Reference | CA |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
A B757 received a low altitude alert on approximately 4 mile final runway 07R. I issued the low altitude alert to the B757 and went over to check the ILS panels. As I was checking the ILS panel; the B757 advised me the glide slope signal was weak; and I noticed that the ILS was set for runway 25L. I configured the ILS for runway 07R and advised the B757 that I had reset the ILS. The B757 continued the approach and landed with out incident. During over ocean traffic; I usually leave the ILS for runway 25L/07R in the west configuration (runway 25L) since we do not use this runway for arrivals and departures due to overnight noise abatement. I had already completed this portion of the watch check list when the city closed runway 25R/07L. I must have forgotten to set the ILS for runway 25L/07R to east configuration (07R) when the city closed runway 25R/07L. I usually visually check the ILS panels when I provide the relief briefing to the relieving flm/controller in charge. While the visually check of the panels is not a requirement; it is a personal preference that I usually perform and did not do this time. Had I stayed with my routine when I was relieved from the ground control/controller in charge position; I would have caught this issue. In the future; I need to stay with my routine.
Original NASA ASRS Text
Title: LAX Tower Controller described a Low Altitude event experienced by a aircraft on final for Runway 7R indicating glide slope difficulties; the reporter acknowledging that the ILS configuration was not changed as needed for this late night operation.
Narrative: A B757 received a Low Altitude Alert on approximately 4 mile final Runway 07R. I issued the Low Altitude Alert to the B757 and went over to check the ILS panels. As I was checking the ILS panel; the B757 advised me the glide slope signal was weak; and I noticed that the ILS was set for Runway 25L. I configured the ILS for Runway 07R and advised the B757 that I had reset the ILS. The B757 continued the approach and landed with out incident. During over ocean traffic; I usually leave the ILS for Runway 25L/07R in the west configuration (Runway 25L) since we do not use this runway for arrivals and departures due to overnight noise abatement. I had already completed this portion of the watch check list when the city closed Runway 25R/07L. I must have forgotten to set the ILS for Runway 25L/07R to east configuration (07R) when the City closed Runway 25R/07L. I usually visually check the ILS panels when I provide the relief briefing to the relieving FLM/CIC. While the visually check of the panels is not a requirement; it is a personal preference that I usually perform and did not do this time. Had I stayed with my routine when I was relieved from the GC/CIC position; I would have caught this issue. In the future; I need to stay with my routine.
Data retrieved from NASA's ASRS site as of July 2013 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.