 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Potential conflict as small transport experiences runway incursion. Unauthorized uncoord runway entry.
| Attributes | |
| ACN | 222817 |
| Time | |
| Date | 199210 |
| Day | Sat |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : arb |
| State Reference | MI |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : arb |
| Operator | general aviation : corporate |
| Make Model Name | Small Transport, Low Wing, 2 Recip Eng |
| Flight Phase | ground other : taxi |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | general aviation : personal |
| Make Model Name | Small Aircraft |
| Flight Phase | descent : approach landing : go around other |
| Flight Plan | None |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : instrument pilot : commercial |
| Experience | flight time last 90 days : 45 flight time total : 750 flight time type : 43 |
| ASRS Report | 222817 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : local |
| Qualification | controller : non radar |
| Events | |
| Anomaly | conflict : ground less severe incursion : runway non adherence : far non adherence : clearance other anomaly other |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | flight crew : took evasive action other other |
| Consequence | faa : reviewed incident with flight crew |
| Miss Distance | horizontal : 500 vertical : 100 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
The airport was very busy with arriving aircraft as well as banner towing aircraft. Upon landing the tower controller instructed me to 'take next taxiway and stay with me.' I took the next taxiway and proceeded to the ramp. The tower controller was very busy with all the traffic in her airspace. The next communication I heard directed to my aircraft was in an excited voice 'small transport X, hold short 30.' upon receiving this communication, I began braking and looking for runway 30. I immediately realized I was about to begin crossing runway 30 which was a sod runway and applied full braking pressure. Simultaneously, a banner pilot executed a go around on 30 as he was flying a low approach to drop a banner. I believe I could have stopped before arriving at runway 30 but the banner pilot was correct in executing the far as there was less margin of safety than normal. The tower then came back and cleared me to cross 30 and said 'didn't you understand my instructions to hold short?' I responded that I had never acknowledged any such instruction (other than the last one which was too late to make a reasonable stop). Later, on the taxi to the ramp, another controller came on and asked me the same question and my response was the same. I am convinced that I was never given 'hold short' instructions prior to the excited instructions which were very late. I also feel that the aircraft could have stopped in time even with the late instructions. On the other hand, I should not have presumed that her instructions cleared me to the ramp even though that often happens when a controller is busy. The factors that influenced this incident, in my opinion, include: my first time in arb. A very busy airport without radar, and 1 controller. A sod runway which isn't as noticeable from the taxiway. Banner airplanes working and intersecting runway from the active (very active, I was second in line to land of 3).
Original NASA ASRS Text
Title: POTENTIAL CONFLICT AS SMT EXPERIENCES RWY INCURSION. UNAUTHORIZED UNCOORD RWY ENTRY.
Narrative: THE ARPT WAS VERY BUSY WITH ARRIVING ACFT AS WELL AS BANNER TOWING ACFT. UPON LNDG THE TWR CTLR INSTRUCTED ME TO 'TAKE NEXT TAXIWAY AND STAY WITH ME.' I TOOK THE NEXT TAXIWAY AND PROCEEDED TO THE RAMP. THE TWR CTLR WAS VERY BUSY WITH ALL THE TFC IN HER AIRSPACE. THE NEXT COM I HEARD DIRECTED TO MY ACFT WAS IN AN EXCITED VOICE 'SMT X, HOLD SHORT 30.' UPON RECEIVING THIS COM, I BEGAN BRAKING AND LOOKING FOR RWY 30. I IMMEDIATELY REALIZED I WAS ABOUT TO BEGIN XING RWY 30 WHICH WAS A SOD RWY AND APPLIED FULL BRAKING PRESSURE. SIMULTANEOUSLY, A BANNER PLT EXECUTED A GAR ON 30 AS HE WAS FLYING A LOW APCH TO DROP A BANNER. I BELIEVE I COULD HAVE STOPPED BEFORE ARRIVING AT RWY 30 BUT THE BANNER PLT WAS CORRECT IN EXECUTING THE FAR AS THERE WAS LESS MARGIN OF SAFETY THAN NORMAL. THE TWR THEN CAME BACK AND CLRED ME TO CROSS 30 AND SAID 'DIDN'T YOU UNDERSTAND MY INSTRUCTIONS TO HOLD SHORT?' I RESPONDED THAT I HAD NEVER ACKNOWLEDGED ANY SUCH INSTRUCTION (OTHER THAN THE LAST ONE WHICH WAS TOO LATE TO MAKE A REASONABLE STOP). LATER, ON THE TAXI TO THE RAMP, ANOTHER CTLR CAME ON AND ASKED ME THE SAME QUESTION AND MY RESPONSE WAS THE SAME. I AM CONVINCED THAT I WAS NEVER GIVEN 'HOLD SHORT' INSTRUCTIONS PRIOR TO THE EXCITED INSTRUCTIONS WHICH WERE VERY LATE. I ALSO FEEL THAT THE ACFT COULD HAVE STOPPED IN TIME EVEN WITH THE LATE INSTRUCTIONS. ON THE OTHER HAND, I SHOULD NOT HAVE PRESUMED THAT HER INSTRUCTIONS CLRED ME TO THE RAMP EVEN THOUGH THAT OFTEN HAPPENS WHEN A CTLR IS BUSY. THE FACTORS THAT INFLUENCED THIS INCIDENT, IN MY OPINION, INCLUDE: MY FIRST TIME IN ARB. A VERY BUSY ARPT WITHOUT RADAR, AND 1 CTLR. A SOD RWY WHICH ISN'T AS NOTICEABLE FROM THE TAXIWAY. BANNER AIRPLANES WORKING AND INTERSECTING RWY FROM THE ACTIVE (VERY ACTIVE, I WAS SECOND IN LINE TO LAND OF 3).
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.