Skyhawk 172/Cutlass 172
Flight Crew Student
Flight Crew Last 90 Days 26; Flight Crew Total 34; Flight Crew Type 32
Training / Qualification; Confusion; Communication Breakdown; Situational Awareness
Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Flight Crew Took Evasive Action
Human Factors
As a student pilot on his second solo cross-country flight; I was preparing to depart ZZZ for ZZZ1. The wind was from 040; so Runway 05 was in use at the time. Looking at the A/FD while parked at the municipal FBO; I deduced that the best way to taxi to Runway 05 was to taxi to Runway 28; then taxi along Runway 28 to the east side of the field; then taxi to the beginning of Runway 05. After brief confusion about how to taxi to the runway (recent construction at ZZZ has blocked the direct taxi route to the intersection of Runways 05 and 28 seen in the A/FD); I taxied up to the hold line for 10/28; made a radio call announcing my intentions to taxi along Runway 28; looked for traffic along and above said runway; and proceeded to turn left onto Runway 28 and begin taxiing. I did not stop before the intersection of the runways and make a radio call; but continued onwards. Approximately 50 feet before the intersection; I observed to my left a recently-landed aircraft on Runway 05 approximately 100 yards from the intersection rolling towards me. Doubting my ability to stop before the intersection; I firewalled the throttle to rapidly cross Runway 05; admitted my error and apologized over the radio; and after a brief stop to gather my nerves; departed and continued my solo cross-country flight. In my opinion; the problem arose due to my lack of familiarity with the airport and complete inexperience with taxiing along intersecting runways. A contributing factor was that I did not hear a call from the other airplane stating that they were on final; which would have warned me of a landing aircraft. Taking these three points in order: This trip was my first experience with traveling to a new airport that I had not previously been to with my instructor. Although I thought I had properly prepared for the flight; I obviously was not fully prepared for operating out of the airfield - especially with the construction having altered the taxiways. I had planned for takeoffs and departures from Runway 10; and had not figured out the return to the departure end of Runway 05 ahead of time when the winds ended up different than expected. Every field that I have flown to before either has parallel taxiways or requires back-taxiing along the departure runway itself. This was my first time ever taxiing along an inactive runway; and I had never crossed a runway intersection when I was not either landing or taking off. While I am obviously required to stop before crossing any runway while taxiing; I am used to stopping before hold lines - and had never had to deal with the absence of one. Right before I announced my intention to taxi onto Runway 28; I heard a call from an airplane on a left downwind for Runway 05. I did not hear a call from any aircraft on base or final; which may have warned me of the impending situation. It is possible that a call was made by the other airplane on long final while I was trying to figure out my taxi path; and I simply missed it due to the distraction. In summary; the cause of this problem was pilot error due to inexperience. The experience gained by this event will hopefully prevent its recurrence. In the meantime; I have grounded myself from flying solo until I can conduct a flight review and another dual cross-country trip with my CFI.
Cessna 172 student pilot reported a ground conflict while taxiing for takeoff. The student added the cause of the problem was pilot error due to inexperience.