 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew of an embraer 120 failed to hold short of parallel runway after landing due to response to another company's clearance with a similar sounding call sign.
| Attributes | |
| ACN | 445589 |
| Time | |
| Date | 199908 |
| Day | Fri |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : lax.airport |
| State Reference | CA |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : orl.tower |
| Operator | common carrier : air carrier |
| Make Model Name | Brasilia EMB-120 All Series |
| Operating Under FAR Part | Part 135 |
| Flight Phase | ground : taxi landing : roll |
| Route In Use | approach : visual |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp pilot : cfi |
| Experience | flight time last 90 days : 200 flight time total : 15000 flight time type : 6000 |
| ASRS Report | 445589 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : atp pilot : cfi pilot : commercial pilot : multi engine |
| Experience | flight time last 90 days : 210 flight time total : 2400 flight time type : 200 |
| ASRS Report | 445609 |
| Events | |
| Anomaly | incursion : runway non adherence : clearance |
| Independent Detector | other controllera |
| Resolutory Action | none taken : detected after the fact none taken : anomaly accepted |
| Consequence | faa : reviewed incident with flight crew Other |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
We were flying our scheduled leg from san to lax. We landed after a visual approach and were in the landing roll. As I was calling for the first officer to start time as per our SOP, the controller gave a clearance for a company aircraft with a similar flight number a clearance to cross runway 25R. My first officer read back, cleared across with our flight number. When we got over to ground control, he told us that we took the other aircraft's clearance. I asked him if I should call the tower and he said no. The factors that contributed were: 1) similar flight number. 2) controller called in landing roll as I was making a required call. 3) our company has started a new numbering system for flight numbers. This has increased the workload and is causing confusion.
Original NASA ASRS Text
Title: FLC OF AN EMBRAER 120 FAILED TO HOLD SHORT OF PARALLEL RWY AFTER LNDG DUE TO RESPONSE TO ANOTHER COMPANY'S CLRNC WITH A SIMILAR SOUNDING CALL SIGN.
Narrative: WE WERE FLYING OUR SCHEDULED LEG FROM SAN TO LAX. WE LANDED AFTER A VISUAL APCH AND WERE IN THE LNDG ROLL. AS I WAS CALLING FOR THE FO TO START TIME AS PER OUR SOP, THE CTLR GAVE A CLRNC FOR A COMPANY ACFT WITH A SIMILAR FLT NUMBER A CLRNC TO CROSS RWY 25R. MY FO READ BACK, CLRED ACROSS WITH OUR FLT NUMBER. WHEN WE GOT OVER TO GND CTL, HE TOLD US THAT WE TOOK THE OTHER ACFT'S CLRNC. I ASKED HIM IF I SHOULD CALL THE TWR AND HE SAID NO. THE FACTORS THAT CONTRIBUTED WERE: 1) SIMILAR FLT NUMBER. 2) CTLR CALLED IN LNDG ROLL AS I WAS MAKING A REQUIRED CALL. 3) OUR COMPANY HAS STARTED A NEW NUMBERING SYS FOR FLT NUMBERS. THIS HAS INCREASED THE WORKLOAD AND IS CAUSING CONFUSION.
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.