docmirror
Touchdown! Greaser!
- Joined
- Jan 5, 2007
- Messages
- 12,008
- Display Name
Display name:
Cowboy - yeehah!
OK, a little while ago I landed at an uncontrolled airport on a straight in. I was tuned to the CTAF well more than 10 miles out, no traffic reports on the radio while I listened. I report '<airport> 10 miles south, planning a straight in to RWY 35<airport>.
At that time, I had the airport in sight, but couldn't make out anything moving from that distance. As I got closer, I reported 5 mile final RWY 35<airport>. Just after that, I distinctly saw some movement down at the 17 end. There is no AWOS but the AWOS nearby had winds at 265@5. There is no 'calm wind' runway defined.
I kept coming, and reported '3 mile final RWY 35<airport>, and clearly saw two planes waiting at the 17 end. They NEVER said a word until I report 3 miles, then one of them transmits '<Name> what does the wind sock show?' And the reply was 'uh, nothing, I don't have <airport> AWOS'.
My final call was '<airport> Bonanza xxx short final RWY 35' and STILL they wouldn't report holding, or taking off, or anything regarding me! Since the runway is crowned, the 17 end can't see the 35 end while on the ground and vice versa. I landed and reported clear of the runway after turning off. I knew they could hear me.
The two planes finally reported a formation takeoff, and after take off reported a STANDARD TRAFFIC PATTERN DEPARTURE in very enunciated words, that I'm sure was aimed at me. Now, I figure if I was making a standard entry, and pattern, they possibly could have taken off in advance of me, but also, I was blistering along on the descent as I usually do, and would have arrived downwind earlier than my arrival on short final, thus blocking them potentially longer.
Sometimes, I can't win. There's been a lot of discussion about whether it's good practice or not. Obviously I think it's fine, as long as I report adequately. It rather galls me that they didn't speak up while sitting at 17. If I'd heard anything during my approach, I would likely have done a std pattern. I thought it was rather petty that they chose to chastise after I'd already set down and got out of the way. The wind wasn't a factor in either direction.
At that time, I had the airport in sight, but couldn't make out anything moving from that distance. As I got closer, I reported 5 mile final RWY 35<airport>. Just after that, I distinctly saw some movement down at the 17 end. There is no AWOS but the AWOS nearby had winds at 265@5. There is no 'calm wind' runway defined.
I kept coming, and reported '3 mile final RWY 35<airport>, and clearly saw two planes waiting at the 17 end. They NEVER said a word until I report 3 miles, then one of them transmits '<Name> what does the wind sock show?' And the reply was 'uh, nothing, I don't have <airport> AWOS'.
My final call was '<airport> Bonanza xxx short final RWY 35' and STILL they wouldn't report holding, or taking off, or anything regarding me! Since the runway is crowned, the 17 end can't see the 35 end while on the ground and vice versa. I landed and reported clear of the runway after turning off. I knew they could hear me.
The two planes finally reported a formation takeoff, and after take off reported a STANDARD TRAFFIC PATTERN DEPARTURE in very enunciated words, that I'm sure was aimed at me. Now, I figure if I was making a standard entry, and pattern, they possibly could have taken off in advance of me, but also, I was blistering along on the descent as I usually do, and would have arrived downwind earlier than my arrival on short final, thus blocking them potentially longer.
Sometimes, I can't win. There's been a lot of discussion about whether it's good practice or not. Obviously I think it's fine, as long as I report adequately. It rather galls me that they didn't speak up while sitting at 17. If I'd heard anything during my approach, I would likely have done a std pattern. I thought it was rather petty that they chose to chastise after I'd already set down and got out of the way. The wind wasn't a factor in either direction.