37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 851848 |
Time | |
Date | 200909 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | TRK.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skylane 182/RG Turbo Skylane/RG |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Person 1 | |
Function | Single Pilot Captain |
Qualification | Flight Crew Private Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 15 Flight Crew Total 1900 Flight Crew Type 1100 |
Events | |
Anomaly | Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 30 |
Narrative:
ASOS reported winds 130 at 7; so I elected to land on runway 19. Two other aircraft reported in the pattern; one landing 28 and the other 10. After exiting runway 19 short of the runway 10/28 intersection; I looked for traffic in the 28 pattern and saw one other aircraft on downwind turning final. Thinking there was enough time to cross 28; I announced my intentions; called the other aircraft in sight and continued toward the intersection of runway 10/28 and runway 19. As I was about to cross runway 10/28; I made one last check and saw a cessna 182 on runway 28 about to takeoff. I managed to stop about 10 feet short of the edge of runway 28 as the cessna aircraft passed directly in front of me. Had I not stopped at that point; there would have been a collision with fatalities. It is possible that I missed position calls from the cessna and I most certainly did not see it in the traffic pattern. The wing strut on my aircraft partially blocked visibility out the left side. I cannot definitively state that the first aircraft (on the runway and on its takeoff roll) did not make any position reports in the pattern; which are clearly voluntary rather than mandatory. It's possible that I was tired and somewhat less attentive after a three hour flight; so I missed radio calls by the first aircraft and as a result did not check the runway as carefully as I should.
Original NASA ASRS Text
Title: A pilot at TRK reported a near ground collision after landing as he neared crossing an intersecting runway after making the appropriate radio calls. Possibly he missed other aircraft position calls because of fatigue.
Narrative: ASOS reported winds 130 at 7; so I elected to land on Runway 19. Two other aircraft reported in the pattern; one landing 28 and the other 10. After exiting Runway 19 short of the Runway 10/28 intersection; I looked for traffic in the 28 pattern and saw one other aircraft on downwind turning final. Thinking there was enough time to cross 28; I announced my intentions; called the other aircraft in sight and continued toward the intersection of Runway 10/28 and Runway 19. As I was about to cross Runway 10/28; I made one last check and saw a Cessna 182 on Runway 28 about to takeoff. I managed to stop about 10 feet short of the edge of Runway 28 as the Cessna aircraft passed directly in front of me. Had I not stopped at that point; there would have been a collision with fatalities. It is possible that I missed position calls from the Cessna and I most certainly did not see it in the traffic pattern. The wing strut on my aircraft partially blocked visibility out the left side. I cannot definitively state that the first aircraft (on the runway and on its takeoff roll) did not make any position reports in the pattern; which are clearly voluntary rather than mandatory. It's possible that I was tired and somewhat less attentive after a three hour flight; so I missed radio calls by the first aircraft and as a result did not check the runway as carefully as I should.
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.