 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Runway 36 incursion by the pilot of a BE40 on rollout runway 9 causes the pilot of a C650 on approach to runway 36 to go around at sav.
| Attributes | |
| ACN | 633198 |
| Time | |
| Date | 200410 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : sav.airport |
| State Reference | GA |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : sav.tower |
| Operator | general aviation : corporate |
| Make Model Name | Beechjet 400 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | ground : taxi landing : roll |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tower : sav.tower |
| Operator | general aviation : corporate |
| Make Model Name | Citation III, VI, VII |
| Operating Under FAR Part | Part 91 |
| Flight Phase | descent : approach landing : go around |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : corporate |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : instrument pilot : commercial pilot : cfi pilot : multi engine pilot : atp |
| Experience | flight time last 90 days : 120 flight time total : 5200 flight time type : 800 |
| ASRS Report | 633198 |
| Person 2 | |
| Affiliation | company : corporate |
| Function | flight crew : first officer |
| Events | |
| Anomaly | conflict : ground less severe incursion : taxiway incursion : runway non adherence : clearance non adherence : required legal separation other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : executed go around flight crew : took evasive action |
| Consequence | faa : reviewed incident with flight crew Other |
| Miss Distance | horizontal : 9000 vertical : 500 |
| Supplementary | |
| Problem Areas | ATC Human Performance Flight Crew Human Performance Airport |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
I had just landed on runway 9 at savana international airport. While on rollout, tower asked if I could make taxiway a, which I said I couldn't (was going too fast), but could make an intersecting runway for the turn-off. The tower replied 'I have traffic on approach runway 36, expedite on taxiway B.' I interpreted this as an aircraft was landing behind me and to turn off on the intersecting runway, then go to taxiway B. Upon turning onto runway 36, I saw a citation 7 on final approach, I then expedited off onto taxiway C, unfortunately, the citation had to go around because of my mistake. This was totally my fault, I had lost situational awareness for a split second and caused a go around. As you can see on the airport diagram, taxiway B doesn't even intersect runway 36, but for some reason I was thinking it did, again, lost situational awareness. I believe this could have been prevented by just being more aware of the txwys and runway layout. We always brief these items and which way we are planning to turn during the approach briefing. Today was no different, we did all of this. Again, this was my fault, I should have studied the diagram more before landing and just kept my situational awareness better than I did. I have learned I will have to be more aware of the airport layout, especially with intersecting approachs in effect. In 14 yrs of flying, that's the first time this has happened to me, but it just goes to show it does happen, even to us that fly everyday. I have learned a valuable lesson, and will strive my best to not let this happen again. I did call the tower, and talked to the pilot of the citation. Everything was ok, but still doesn't excuse what happened.
Original NASA ASRS Text
Title: RWY 36 INCURSION BY THE PLT OF A BE40 ON ROLLOUT RWY 9 CAUSES THE PLT OF A C650 ON APCH TO RWY 36 TO GO AROUND AT SAV.
Narrative: I HAD JUST LANDED ON RWY 9 AT SAVANA INTL ARPT. WHILE ON ROLLOUT, TWR ASKED IF I COULD MAKE TXWY A, WHICH I SAID I COULDN'T (WAS GOING TOO FAST), BUT COULD MAKE AN INTERSECTING RWY FOR THE TURN-OFF. THE TWR REPLIED 'I HAVE TFC ON APCH RWY 36, EXPEDITE ON TXWY B.' I INTERPED THIS AS AN ACFT WAS LNDG BEHIND ME AND TO TURN OFF ON THE INTERSECTING RWY, THEN GO TO TXWY B. UPON TURNING ONTO RWY 36, I SAW A CITATION 7 ON FINAL APCH, I THEN EXPEDITED OFF ONTO TXWY C, UNFORTUNATELY, THE CITATION HAD TO GO AROUND BECAUSE OF MY MISTAKE. THIS WAS TOTALLY MY FAULT, I HAD LOST SITUATIONAL AWARENESS FOR A SPLIT SECOND AND CAUSED A GAR. AS YOU CAN SEE ON THE ARPT DIAGRAM, TXWY B DOESN'T EVEN INTERSECT RWY 36, BUT FOR SOME REASON I WAS THINKING IT DID, AGAIN, LOST SITUATIONAL AWARENESS. I BELIEVE THIS COULD HAVE BEEN PREVENTED BY JUST BEING MORE AWARE OF THE TXWYS AND RWY LAYOUT. WE ALWAYS BRIEF THESE ITEMS AND WHICH WAY WE ARE PLANNING TO TURN DURING THE APCH BRIEFING. TODAY WAS NO DIFFERENT, WE DID ALL OF THIS. AGAIN, THIS WAS MY FAULT, I SHOULD HAVE STUDIED THE DIAGRAM MORE BEFORE LNDG AND JUST KEPT MY SITUATIONAL AWARENESS BETTER THAN I DID. I HAVE LEARNED I WILL HAVE TO BE MORE AWARE OF THE ARPT LAYOUT, ESPECIALLY WITH INTERSECTING APCHS IN EFFECT. IN 14 YRS OF FLYING, THAT'S THE FIRST TIME THIS HAS HAPPENED TO ME, BUT IT JUST GOES TO SHOW IT DOES HAPPEN, EVEN TO US THAT FLY EVERYDAY. I HAVE LEARNED A VALUABLE LESSON, AND WILL STRIVE MY BEST TO NOT LET THIS HAPPEN AGAIN. I DID CALL THE TWR, AND TALKED TO THE PLT OF THE CITATION. EVERYTHING WAS OK, BUT STILL DOESN'T EXCUSE WHAT HAPPENED.
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.