 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier first officer reported encountering closed taxiways at cho that were not included in notams for their arrival time.
| Attributes | |
| ACN | 1482895 |
| Time | |
| Date | 201709 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | CHO.Airport |
| State Reference | VA |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Person 1 | |
| Function | First Officer Pilot Not Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Ground Incursion Taxiway |
Narrative:
Upon landing cho runway 03 after the tower closed; we turned onto taxiway G to find the taxiway partially blocked with sandbags and small; dim flashing lights. The captain immediately stopped the aircraft to assess the situation. As a crew we looked outside at sign-age to determine our exact position on G. We also verified by rechecking the notams that taxiway G was not a closed taxiway. I repeatedly tried to contact ops for help but they were unavailable. It was obvious that we did not have enough room to turn around and there was no danger of continuing forward; so we cautiously proceeded forward with no incident. Once we made the turn from G onto taxiway a; we realized that taxiway a was also barricaded ahead. At that point we stopped and called our dispatcher. By that time the airport police came and removed the barricades so we could continue to the terminal without further incident. After talking to dispatch; there seemed to be no notams relating to the closure of taxiways G and a. Later the next day I checked the notams for kcho on the internet to find they were now posted but valid from 0010 local; after our arrival time. Obviously there were no notams of the closures for our arrival time.
Original NASA ASRS Text
Title: Air Carrier First Officer reported encountering closed taxiways at CHO that were not included in NOTAMs for their arrival time.
Narrative: Upon landing CHO Runway 03 after the Tower closed; we turned onto Taxiway G to find the taxiway partially blocked with sandbags and small; dim flashing lights. The Captain immediately stopped the aircraft to assess the situation. As a crew we looked outside at sign-age to determine our exact position on G. We also verified by rechecking the NOTAMs that Taxiway G was not a closed taxiway. I repeatedly tried to contact Ops for help but they were unavailable. It was obvious that we did not have enough room to turn around and there was no danger of continuing forward; so we cautiously proceeded forward with no incident. Once we made the turn from G onto Taxiway A; we realized that Taxiway A was also barricaded ahead. At that point we stopped and called our Dispatcher. By that time the Airport Police came and removed the Barricades so we could continue to the terminal without further incident. After talking to Dispatch; there seemed to be no NOTAMs relating to the closure of Taxiways G and A. Later the next day I checked the NOTAMs for KCHO on the internet to find they were now posted but valid from 0010 local; after our arrival time. Obviously there were no NOTAMs of the closures for our arrival time.
Data retrieved from NASA's ASRS site 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.