37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 844710 |
Time | |
Date | 200907 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Cessna 336 Skymaster |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Single Pilot |
Qualification | Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Multiengine |
Experience | Flight Crew Total 1350 |
Events | |
Anomaly | Deviation - Procedural Clearance Ground Event / Encounter Other / Unknown Ground Incursion Runway |
Narrative:
Upon landing on runway 24L; I requested taxi clearance to the FBO. I was instructed to turn left on taxiway D then left on runway 36 and to turn right on taxiway H. I explained I was unfamiliar with the airport and the controller told me to taxi up on runway 36 and to take taxiway H to the right. We taxied forward on runway 36 looking ahead. We did not see a taxiway sign for H and we crossed runway 24L. As we were crossing runway 24L I told the controller that we were still looking for taxiway H. The controller told us to make a 180 degree turn and I asked for clearance to cross runway 24L. I told the controller we did not see a sign for taxiway H while on runway 36; but we saw one coming back on runway 18. There was no conflict and rest of taxi was uneventful. This showed the importance of using airport diagram and not depending solely on controllers. I also realized that I was more tired than I realized. This occurred after a multi-day trip that originated in mexico with family and made many stops. I decided to leave the airplane in dayton and continue by car with friends until I had sufficient time to rest. I feel this was a combination of exhaustion; depending on the controller when I stated that I was unfamiliar with the airport and not stopping the aircraft to locate our position on the airport diagram. I saw the runway 24L sign but it did not register that I had not received a specific clearance to cross until I was already crossing -- exhaustion.
Original NASA ASRS Text
Title: Fatigued pilot at DAY found himself confused as to his location and relying heavily on ATC progressive taxi instructions rather than utilizing an airport diagram.
Narrative: Upon landing on Runway 24L; I requested taxi clearance to the FBO. I was instructed to turn left on Taxiway D then left on Runway 36 and to turn right on Taxiway H. I explained I was unfamiliar with the airport and the Controller told me to taxi up on Runway 36 and to take Taxiway H to the right. We taxied forward on Runway 36 looking ahead. We did not see a taxiway sign for H and we crossed Runway 24L. As we were crossing Runway 24L I told the Controller that we were still looking for Taxiway H. The Controller told us to make a 180 degree turn and I asked for clearance to cross Runway 24L. I told the Controller we did not see a sign for Taxiway H while on Runway 36; but we saw one coming back on Runway 18. There was no conflict and rest of taxi was uneventful. This showed the importance of using airport diagram and not depending solely on controllers. I also realized that I was more tired than I realized. This occurred after a multi-day trip that originated in Mexico with family and made many stops. I decided to leave the airplane in Dayton and continue by car with friends until I had sufficient time to rest. I feel this was a combination of exhaustion; depending on the controller when I stated that I was unfamiliar with the airport and not stopping the aircraft to locate our position on the airport diagram. I saw the Runway 24L sign but it did not register that I had not received a specific clearance to cross until I was already crossing -- exhaustion.
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.