Narrative:

I was leaving ZZZ where I am based to do practice landings [another airport]. Taxing out of the [parking area] I stopped and requested xx because the sock suggested it was slightly favored; although most the wind was across the runway. The controller indicated that it was unavailable due to pattern work on 28R and I believe offered me 33R or xy before issuing a clearance. I began taxiing to 33R via x-y. As I approached the xy threshold; I was unclear in my head whether I had been cleared to cross xy and initiated braking. Due to a significant tailwind; the braking was less effective than anticipated and I pushed harder on the brakes; which caused the tail to leave the ground and the prop to strike the taxiway. This initial strike occurred before the hold short line.after the initial strike I believe I let my feet off the brakes briefly before pushing them even harder; which caused a second prop strike and the aircraft to roll up on its nose. The aircraft came to a stop roughly 10-15 feet past the hold short line. In conversation with the ATC supervisor; who had reviewed the tapes; I was told later that in fact I had been cleared to xy via x-y. This came as a surprise to me; as the question in my mind was whether or not I had been cleared to cross or asked to hold short; which was my expectation of what the controller would have said explicitly relative to the past when a clearance to 33R would have implied a clearance to cross xy. This confusion leads me to believe that the sequence of runways discussed; plus the aircraft that was already in the pattern on 33R caused me to 'hear' something different that was actually said. I'm not sure what would have been better from a clarification perspective other than if I had heard 'hold short' 33R but that would have been non-standard for a clearance to 33R. I believe that my familiarity with the airport was actually a hindrance in this case as it may have led to my being less vigilant than would be typical if I were unfamiliar.

Related reports:

Google
 

Original NASA ASRS Text

Title: c180 pilot reported braking suddenly due to a confused taxi clearance; resulting in a prop-strike.

Narrative: I was leaving ZZZ where I am based to do practice landings [another airport]. Taxing out of the [parking area] I stopped and requested XX because the sock suggested it was slightly favored; although most the wind was across the runway. The controller indicated that it was unavailable due to pattern work on 28R and I believe offered me 33R or XY before issuing a clearance. I began taxiing to 33R via X-Y. As I approached the XY threshold; I was unclear in my head whether I had been cleared to cross XY and initiated braking. Due to a significant tailwind; the braking was less effective than anticipated and I pushed harder on the brakes; which caused the tail to leave the ground and the prop to strike the taxiway. This initial strike occurred before the hold short line.After the initial strike I believe I let my feet off the brakes briefly before pushing them even harder; which caused a second prop strike and the aircraft to roll up on its nose. The aircraft came to a stop roughly 10-15 feet past the hold short line. In conversation with the ATC supervisor; who had reviewed the tapes; I was told later that in fact I had been cleared to XY via X-Y. This came as a surprise to me; as the question in my mind was whether or not I had been cleared to cross or asked to hold short; which was my expectation of what the controller would have said explicitly relative to the past when a clearance to 33R would have implied a clearance to cross XY. This confusion leads me to believe that the sequence of runways discussed; plus the aircraft that was already in the pattern on 33R caused me to 'hear' something different that was actually said. I'm not sure what would have been better from a clarification perspective other than if I had heard 'hold short' 33R but that would have been non-standard for a clearance to 33R. I believe that my familiarity with the airport was actually a hindrance in this case as it may have led to my being less vigilant than would be typical if I were unfamiliar.

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.