 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An MD88 flight crew is vectored for a second approach when the second approach controller advises them that they had overshot the localizer for runway 27L. The crew had previously been set up for the ILS to runway 26R by the first approach controller at atl, GA.
| Attributes | |
| ACN | 483090 |
| Time | |
| Date | 200008 |
| Day | Thu |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : atl.airport |
| State Reference | GA |
| Altitude | msl single value : 3500 |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : atl.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | MD-88 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | ils localizer & glide slope : 26r other other vortac |
| Flight Phase | descent : intermediate altitude |
| Route In Use | approach : instrument precision arrival : on vectors |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : multi engine pilot : atp |
| Experience | flight time last 90 days : 100 flight time total : 8500 flight time type : 4700 |
| ASRS Report | 483090 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument pilot : multi engine |
| Events | |
| Anomaly | non adherence : published procedure non adherence : clearance other anomaly other other spatial deviation |
| Independent Detector | other controllera |
| Resolutory Action | controller : issued new clearance controller : issued advisory other |
| Consequence | faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance Airspace Structure ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Deviation Intra Facility Coordination Failure |
Narrative:
Upon initial contact with approach control we were told to expect ILS runway 26R. After switching to the next controller he cleared us for the ILS. We had runway 26R tuned in, but evidently he cleared us for runway 27L. He informed us that we were going through the localizer for runway 27L. There were no traffic conflicts that we were aware of. When cleared for the ILS, I read back 'cleared for the ILS runway 26R,' but the radios being very busy, the controller didn't catch the 'runway 26R' portion that I read back. He vectored us back around for runway 27L. This situation wasn't any one person's fault, just an unfortunate chain of events.
Original NASA ASRS Text
Title: AN MD88 FLC IS VECTORED FOR A SECOND APCH WHEN THE SECOND APCH CTLR ADVISES THEM THAT THEY HAD OVERSHOT THE LOC FOR RWY 27L. THE CREW HAD PREVIOUSLY BEEN SET UP FOR THE ILS TO RWY 26R BY THE FIRST APCH CTLR AT ATL, GA.
Narrative: UPON INITIAL CONTACT WITH APCH CTL WE WERE TOLD TO EXPECT ILS RWY 26R. AFTER SWITCHING TO THE NEXT CTLR HE CLRED US FOR THE ILS. WE HAD RWY 26R TUNED IN, BUT EVIDENTLY HE CLRED US FOR RWY 27L. HE INFORMED US THAT WE WERE GOING THROUGH THE LOC FOR RWY 27L. THERE WERE NO TFC CONFLICTS THAT WE WERE AWARE OF. WHEN CLRED FOR THE ILS, I READ BACK 'CLRED FOR THE ILS RWY 26R,' BUT THE RADIOS BEING VERY BUSY, THE CTLR DIDN'T CATCH THE 'RWY 26R' PORTION THAT I READ BACK. HE VECTORED US BACK AROUND FOR RWY 27L. THIS SIT WASN'T ANY ONE PERSON'S FAULT, JUST AN UNFORTUNATE CHAIN OF EVENTS.
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.