37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 495858 |
Time | |
Date | 200012 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : pit.airport |
State Reference | PA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tower : mco.tower |
Operator | general aviation : corporate |
Make Model Name | Gulfstream II |
Operating Under FAR Part | Part 91 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : pit.tower |
Operator | common carrier : air taxi |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 135 |
Flight Phase | ground : taxi |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 160 flight time total : 2900 flight time type : 1300 |
ASRS Report | 495858 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Events | |
Anomaly | incursion : runway non adherence : clearance |
Independent Detector | other controllera other controllerb |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | ATC Human Performance Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On dec/xa/00, we called for taxi clearance at pit. The controller asked if we were familiar with the airport and issued a taxi clearance. Acknowledging our unfamiliarity, we were issued further instructions to follow a commuter airliner on taxiway P. There was an absence of runway and hold short instructions. We then crossed runway 28C and fell in behind the commuter following them to runway 28L. After the commuter turned onto runway 28L, I asked the controller if we were to continue following him. The controller's response was yes. We continued our taxi onto runway 28L and then realized the commuter was on their takeoff roll. Ground immediately switched us to tower and we proceeded with a normal takeoff. I believe the following factors may have contributed to the inadvertent incursion: 1) crew unfamiliarity. 2) crew fatigue. 3) controller workload. 4) lack of specific instructions.
Original NASA ASRS Text
Title: GLF2 CREW HAD RWY INCURSION AT RWY 28L AT PIT.
Narrative: ON DEC/XA/00, WE CALLED FOR TAXI CLRNC AT PIT. THE CTLR ASKED IF WE WERE FAMILIAR WITH THE ARPT AND ISSUED A TAXI CLRNC. ACKNOWLEDGING OUR UNFAMILIARITY, WE WERE ISSUED FURTHER INSTRUCTIONS TO FOLLOW A COMMUTER AIRLINER ON TXWY P. THERE WAS AN ABSENCE OF RWY AND HOLD SHORT INSTRUCTIONS. WE THEN CROSSED RWY 28C AND FELL IN BEHIND THE COMMUTER FOLLOWING THEM TO RWY 28L. AFTER THE COMMUTER TURNED ONTO RWY 28L, I ASKED THE CTLR IF WE WERE TO CONTINUE FOLLOWING HIM. THE CTLR'S RESPONSE WAS YES. WE CONTINUED OUR TAXI ONTO RWY 28L AND THEN REALIZED THE COMMUTER WAS ON THEIR TKOF ROLL. GND IMMEDIATELY SWITCHED US TO TWR AND WE PROCEEDED WITH A NORMAL TKOF. I BELIEVE THE FOLLOWING FACTORS MAY HAVE CONTRIBUTED TO THE INADVERTENT INCURSION: 1) CREW UNFAMILIARITY. 2) CREW FATIGUE. 3) CTLR WORKLOAD. 4) LACK OF SPECIFIC INSTRUCTIONS.
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.