37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1563936 |
Time | |
Date | 201807 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | HOM.Airport |
State Reference | AK |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 135 |
Flight Phase | Taxi |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | Landing |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Commercial |
Experience | Flight Crew Last 90 Days 150 Flight Crew Total 1800 Flight Crew Type 400 |
Events | |
Anomaly | Conflict Ground Conflict Less Severe Ground Incursion Runway |
Narrative:
Got ATIS information from homer radio; and called in for a traffic advisory while taxiing to the runway. Runway 22 at homer only has taxiways near the approach end of runway 4. A back-taxi on the runway is required to use runway 22. I was at the middle taxiway. Homer radio provided the traffic advisory; and stated there were two float planes on the downwind to land on the lake (which has an opposite traffic pattern from runway). I had both of the float planes in sight; and they were not going to be a factor. I scanned the runway and the final approach path of runway 22 and saw no aircraft. I announced that I was back taxiing on runway 22; and pulled across the hold short line. My nose had just entered the runway when I saw an airplane coming down runway 22 on the roll out. He pulled off on the taxiway prior to the one I was using and called clear of the runway.I have no idea how I didn't see him. I was very surprised; and can't remember if his lights were on. Contributing factors may have been that I was in a slight hurry because I was running about 10 minutes behind schedule; and that flight was my sixth departure from homer that day so a little fatigue came into play as well. Complacency was probably also a factor. Homer radio called out the traffic; but I did not hear them mention the aircraft on roll out on 22; if they even mentioned it; which I don't believe they did. I also scanned the runway pretty diligently before entering the runway; but somehow I still didn't see that aircraft. White aircraft are pretty difficult to see when going over large white runway stripes. The runway is also; convex; which can make traffic father down runway 22 harder to see.I have been an advocate; for a long time; about putting in a taxiway that extends full length down runway 22. The traffic flow on runway 22 can get pretty intense when aircraft are landing and multiple aircraft are waiting to back taxi; and can cause people to rush to back taxi in-between aircraft in the pattern. In the future; I'll slow down; and fight complacency with a good traffic scan. If that had been an aircraft on takeoff; the outcome of this event could have been very different.
Original NASA ASRS Text
Title: Air taxi Pilot entering the takeoff runway for back taxi; reported a ground conflict with another aircraft that was on landing roll out.
Narrative: Got ATIS information from Homer radio; and called in for a traffic advisory while taxiing to the runway. Runway 22 at Homer only has taxiways near the approach end of runway 4. A back-taxi on the runway is required to use runway 22. I was at the middle taxiway. Homer radio provided the traffic advisory; and stated there were two float planes on the downwind to land on the lake (which has an opposite traffic pattern from runway). I had both of the float planes in sight; and they were not going to be a factor. I scanned the runway and the final approach path of runway 22 and saw no aircraft. I announced that I was back taxiing on runway 22; and pulled across the hold short line. My nose had just entered the runway when I saw an airplane coming down runway 22 on the roll out. He pulled off on the taxiway prior to the one I was using and called clear of the runway.I have no idea how I didn't see him. I was very surprised; and can't remember if his lights were on. Contributing factors may have been that I was in a slight hurry because I was running about 10 minutes behind schedule; and that flight was my sixth departure from Homer that day so a little fatigue came into play as well. Complacency was probably also a factor. Homer radio called out the traffic; but I did not hear them mention the aircraft on roll out on 22; if they even mentioned it; which I don't believe they did. I also scanned the runway pretty diligently before entering the runway; but somehow I still didn't see that aircraft. White aircraft are pretty difficult to see when going over large white runway stripes. The runway is also; convex; which can make traffic father down runway 22 harder to see.I have been an advocate; for a long time; about putting in a taxiway that extends full length down runway 22. The traffic flow on runway 22 can get pretty intense when aircraft are landing and multiple aircraft are waiting to back taxi; and can cause people to rush to back taxi in-between aircraft in the pattern. In the future; I'll slow down; and fight complacency with a good traffic scan. If that had been an aircraft on takeoff; the outcome of this event could have been very different.
Data retrieved from NASA's ASRS site 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.