37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 823397 |
Time | |
Date | 200902 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PDK.Airport |
State Reference | GA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft Low Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Private |
Experience | Flight Crew Last 90 Days 32 Flight Crew Total 722 Flight Crew Type 500 |
Person 2 | |
Function | Local |
Events | |
Anomaly | Conflict Ground Conflict Critical Deviation - Procedural Clearance Ground Incursion Runway |
Miss Distance | Horizontal 100 Vertical 0 |
Narrative:
I was returning to pdk (atlanta/dekalb peachtree) on an instrument filed flight plan. I was cleared to land on runway 20L and; upon landing; I believed my clearance from the tower controller to be exit right on taxiway D; cross runway 20R; hold on the other side and remain on the tower frequency; and this is the clearance I believe I read back. It is the clearance I wrote down on my kneeboard pad. Believing this to be my clearance; I exited runway 20L to the right onto taxiway D; and proceeded through the hold short line on taxiway D between runway 20L and runway 20R toward the crossing of taxiway D with runway 20R. Upon taxiing through this hold short line; I did not receive any call or communication from the tower directing me to stop; hold; or in any way indicating that I was violating an authorization or that I was not cleared to cross runway 20R on taxiway D; and this lack of any such com further reinforced my belief that I was cleared to cross runway 20R. As I was crossing runway 20R I saw another aircraft either landing or departing runway 20R approaching my aircraft from the right. Again; I had not had any communication between the tower controller and the other aircraft indicating that a conflict existed between the aircraft or the clearance that had been provided. Inasmuch as I was already taxiing through runway 20R when I first saw the approaching aircraft; upon seeing the approaching aircraft on runway 20R I had no choice but to proceed on through runway 20R on taxiway D in order to avoid the prospect of conflict with the other aircraft. I did so and as I did; the other aircraft passed behind my aircraft on runway 20R. At no time did I ever hear any communication between this aircraft and the tower; not had the tower communicated with me any further since my initial taxi clearance had been issued. I do not believe the other aircraft was at any time required to leave runway 20R in order to avoid any conflict; and I was not required to leave taxiway D in order to avoid any potential conflict. Upon reaching the hold short line on taxiway D on the other side of runway 20R I was; for the first time since the earlier clearance was issued; contacted by the tower controller and advised that an event that might require reporting had just occurred; given a telephone number and asked to call the tower. I did so approximately 10 minutes later upon taxiing and exiting my aircraft.
Original NASA ASRS Text
Title: A light aircraft pilot experienced a conflict with another aircraft as he crossed a runway. He thought he was cleared to cross; Local Control felt otherwise.
Narrative: I was returning to PDK (Atlanta/DeKalb Peachtree) on an instrument filed flight plan. I was cleared to land on Runway 20L and; upon landing; I believed my clearance from the Tower Controller to be exit right on Taxiway D; cross Runway 20R; hold on the other side and remain on the Tower Frequency; and this is the clearance I believe I read back. It is the clearance I wrote down on my kneeboard pad. Believing this to be my clearance; I exited Runway 20L to the right onto Taxiway D; and proceeded through the hold short line on Taxiway D between Runway 20L and Runway 20R toward the crossing of Taxiway D with Runway 20R. Upon taxiing through this hold short line; I did not receive any call or communication from the Tower directing me to stop; hold; or in any way indicating that I was violating an authorization or that I was not cleared to cross Runway 20R on Taxiway D; and this lack of any such com further reinforced my belief that I was cleared to cross Runway 20R. As I was crossing Runway 20R I saw another aircraft either landing or departing Runway 20R approaching my aircraft from the right. Again; I had not had any communication between the Tower Controller and the other aircraft indicating that a conflict existed between the aircraft or the clearance that had been provided. Inasmuch as I was already taxiing through Runway 20R when I first saw the approaching aircraft; upon seeing the approaching aircraft on Runway 20R I had no choice but to proceed on through Runway 20R on Taxiway D in order to avoid the prospect of conflict with the other aircraft. I did so and as I did; the other aircraft passed behind my aircraft on Runway 20R. At no time did I ever hear any communication between this aircraft and the Tower; not had the Tower communicated with me any further since my initial taxi clearance had been issued. I do not believe the other aircraft was at any time required to leave Runway 20R in order to avoid any conflict; and I was not required to leave Taxiway D in order to avoid any potential conflict. Upon reaching the hold short line on Taxiway D on the other side of Runway 20R I was; for the first time since the earlier clearance was issued; contacted by the Tower Controller and advised that an event that might require reporting had just occurred; given a telephone number and asked to call the Tower. I did so approximately 10 minutes later upon taxiing and exiting my aircraft.
Data retrieved from NASA's ASRS site as of April 2012 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.