 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Corporate jet flight crew reported a runway incursion due to ground controller's ambiguity and lack of situational awareness.
| Attributes | |
| ACN | 1602681 |
| Time | |
| Date | 201812 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | VNY.Airport |
| State Reference | CA |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | Light Transport |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Taxi |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Not Flying |
| Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
| Person 2 | |
| Function | Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | ATC Issue All Types Conflict Ground Conflict Critical Ground Incursion Runway |
Narrative:
We were repositioning from FBO 1 where we cleared customs and dropped clients over to FBO 2 to prepare to depart for [destination]. We were given clearance to taxi via alpha and papa to hold short of [runway] 16R. After being told to hold a couple of minutes for other crossing traffic we were given clearance to cross [runway] 16R at papa and to join bravo to FBO. About 10 seconds after being cleared to cross; ground instructs us to hold short immediately for landing traffic. We advised we were already across the hold short line based on the earlier clearance. We were then cleared to cross once again expeditiously. The other GA aircraft on short final was sent around as a runway incursion would have followed due to our inability to be completely across the hold short line in time.the ground controller seemed a bit overwhelmed due to the amount of GA traffic in the pattern and taxiing for [runway] 16L. We were vigilant in keeping up with what was going on on the ground and did not see much margin for incursions as separate runways were being utilized for GA and jet traffic.when there is a busy traffic pattern double verifying cleared across runway instructions.
Original NASA ASRS Text
Title: Corporate jet flight crew reported a runway incursion due to Ground Controller's ambiguity and lack of situational awareness.
Narrative: We were repositioning from FBO 1 where we cleared Customs and dropped clients over to FBO 2 to prepare to depart for [destination]. We were given clearance to taxi via Alpha and Papa to hold short of [Runway] 16R. After being told to hold a couple of minutes for other crossing traffic we were given clearance to cross [Runway] 16R at Papa and to join Bravo to FBO. About 10 seconds after being cleared to cross; Ground instructs us to hold short immediately for landing traffic. We advised we were already across the hold short line based on the earlier clearance. We were then cleared to cross once again expeditiously. The other GA aircraft on short final was sent around as a runway incursion would have followed due to our inability to be completely across the hold short line in time.The Ground Controller seemed a bit overwhelmed due to the amount of GA traffic in the pattern and taxiing for [Runway] 16L. We were vigilant in keeping up with what was going on on the ground and did not see much margin for incursions as separate runways were being utilized for GA and jet traffic.When there is a busy traffic pattern double verifying cleared across runway instructions.
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.