 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Runway incursion by a B737-300 flight crew when the PIC receives and acknowledges a crossing clearance for runway 22 at hou, tx.
| Attributes | |
| ACN | 613508 |
| Time | |
| Date | 200404 |
| Day | Thu |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : hou.airport |
| State Reference | TX |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : hou.tower tower : hou.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : holding ground : taxi |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tower : hou.tower |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | descent : approach |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : multi engine pilot : commercial |
| Experience | flight time last 90 days : 220 flight time total : 12000 flight time type : 5000 |
| ASRS Report | 613508 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | conflict : ground less severe incursion : runway non adherence : published procedure non adherence : clearance |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Consequence | faa : investigated faa : reviewed incident with flight crew |
| Supplementary | |
| Problem Areas | Environmental Factor ATC Human Performance Flight Crew Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Intra Facility Coordination Failure |
Narrative:
After landing at hobby, we were cleared to taxi on taxiway C and to hold short of runway 22. I went off frequency to call company. While off frequency, I heard the captain read back 'cross runway 22.' I came back on frequency. The captain told me we were cleared to cross runway 22. There was an aircraft landing on runway 12R and another taxiing into position on runway 22, so all seemed normal. Upon crossing runway 22, ground told us that we were not cleared to cross. The captain responded that we had been and that he had read back the clearance. Ground reaffirmed that we had not been cleared and that the readback had been blocked. Later, we called tower and found that there had been some confusion with an aircraft with a similar call sign. There was no safety concern as far as us crossing when we did, just confusion as to what we had been instructed to do.
Original NASA ASRS Text
Title: RWY INCURSION BY A B737-300 FLT CREW WHEN THE PIC RECEIVES AND ACKNOWLEDGES A XING CLRNC FOR RWY 22 AT HOU, TX.
Narrative: AFTER LNDG AT HOBBY, WE WERE CLRED TO TAXI ON TXWY C AND TO HOLD SHORT OF RWY 22. I WENT OFF FREQ TO CALL COMPANY. WHILE OFF FREQ, I HEARD THE CAPT READ BACK 'CROSS RWY 22.' I CAME BACK ON FREQ. THE CAPT TOLD ME WE WERE CLRED TO CROSS RWY 22. THERE WAS AN ACFT LNDG ON RWY 12R AND ANOTHER TAXIING INTO POS ON RWY 22, SO ALL SEEMED NORMAL. UPON XING RWY 22, GND TOLD US THAT WE WERE NOT CLRED TO CROSS. THE CAPT RESPONDED THAT WE HAD BEEN AND THAT HE HAD READ BACK THE CLRNC. GND REAFFIRMED THAT WE HAD NOT BEEN CLRED AND THAT THE READBACK HAD BEEN BLOCKED. LATER, WE CALLED TWR AND FOUND THAT THERE HAD BEEN SOME CONFUSION WITH AN ACFT WITH A SIMILAR CALL SIGN. THERE WAS NO SAFETY CONCERN AS FAR AS US XING WHEN WE DID, JUST CONFUSION AS TO WHAT WE HAD BEEN INSTRUCTED TO DO.
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.