Bonehead move today

Went to Lone Rock, Wisconsin today for the $100 hamburger , with excellent
VFR conditions, and winds light and variable.

After lunch we saw a 210 taxi to the approach end of runway 27 (clearly
visible from the the far end at the restaurant). Just as he started his
takeoff roll, another guy in a 152 taxied onto runway 9, and announced his
departure from runway 9! (yes the opposite direction, with another plane
coming directly at him down the runway.

The 210 did a very steep climb straight ahead, while the 152 did some pretty
radical low level maneuvering to avoid a head on collision. Perhaps the guy
in the 152 assumed the 210 had departed on 09 (there are no taxiways, so
everything is a back taxi, and the winds were light and variable), and the
guy in the 210 wasn't taking at all over unicom, but even so, the far end of
the runway was clearly visible, and there was a big as life 210 rolling in
the opposite direction.

It was about as close to a catastrophe as I'd ever seen, and the guy in my
right seat (CFI, multi, etc) agreed that the guy in the 152 probably never
looked. I'm not sure what to learn from theexperience, but it sure looked
like someone wasn't paying attention.

Did the 210 make any announcements?

Wouldn't be surprised if the 152 had announced his back taxi a few
minutes earlier and wasn't really listening after that, even if the 210
anounced. That runway is what, 5K? (I fly out of Morey). Thats a long
taxi for any plane.

John

The 210 taxied from the hangar next to the restaurant all of the way to the
far end of the runway, while the 152 simply taxied from the restaurant
directly onto 9 and departed.

As I recall, the 210 only announced his taxi prior to going down the runway,
while the 152 said Cessna xxx departing runway 9, Lone Rock.

They converged at approximately midfield, with the 152 taking evasive action
by doing a steep right turn to the south away from the runway at low
altitude, while the 210 climbed on runway heading and did not take any
obvious evasive action. The 210 did not announce his takeoff roll, but he
clearly was on the runway and visible from the far end (where we were parked
in front of the restaurant). It happened so fast and we hadn't powered up
yet, so couldn't even have given a warning call on the radio.

It's hard to say, but from our perspective it looked like they came within
100 feet or less. In my opinion it was clearly the fault of the 152. For a
few brief moments there was a lot of traffic- a 337 landed, a Mooney was
running up, a Stearman departed, and we were cranking in the Baron, in
addition to the 152 and 210- a lot going on for a small uncontrolled field.

For a
few brief moments there was a lot of traffic- a 337 landed, a Mooney was
running up, a Stearman departed, and we were cranking in the Baron, in
addition to the 152 and 210- a lot going on for a small uncontrolled
field.


Sounds like the last time I was there. Traffic was using 27, so everybody
had to back taxi from the restaurant. When I was 1/2 way down, a plane
announced turning base to final, so I pulled off at one of the run-up areas
midway down the runway. I bet I waited there with both props spinning for
at least 4 planes to land before I got back out on the runway to finish my
taxi to the end.

Jim

Viperdoc wrote:

The 210 taxied from the hangar next to the restaurant all of the way to the
far end of the runway, while the 152 simply taxied from the restaurant
directly onto 9 and departed.

As I recall, the 210 only announced his taxi prior to going down the runway,
while the 152 said Cessna xxx departing runway 9, Lone Rock.

They converged at approximately midfield, with the 152 taking evasive action
by doing a steep right turn to the south away from the runway at low
altitude, while the 210 climbed on runway heading and did not take any
obvious evasive action. The 210 did not announce his takeoff roll, but he
clearly was on the runway and visible from the far end (where we were parked
in front of the restaurant). It happened so fast and we hadn't powered up
yet, so couldn't even have given a warning call on the radio.

I agree that the 152 should have looked down the runway before
commencing his take-off roll, however, so should the 210 pilot. And if
the 210 pilot really didn't announce his intent to depart 27, then I'd
place the blame primarily on him/her.


Matt

Neither pilot had an obligation to announce anything on the radio.

While neither pilot had any obligation to announce, if I had been in the 210
and somebody made a radio call saying they were departing off of the same
runway in the opposite direction it probably would have gotten my attention.

Neither pilot had an obligation to announce anything on the radio.

Pilots aren't obligated by FAR to breathe, either -- but it's highly
recommended.

;-)
--
Jay Honeck
Iowa City, IA
Pathfinder N56993
www.AlexisParkInn.com
"Your Aviation Destination"

This is where common sense vs "by the book" conflict. You are correct
that "by the book" they didn't have to announce anything. However,
common sense tells us this was / is not the best course of action.

Anytime someone tells me he/she "flies strictly by the book", I pay 300%
more attention to what they are doing!! They ten d to be the most
dangerous pilots..IMO. The "book" is a good outline for structure, but
you must fill in the Chapters and pages with good common sense to be safe.

BJ

Brien K. Meehan wrote:

Neither pilot had an obligation to announce anything on the radio.

That is a lot of traffic for LNR...I've landed there about 3-4 times,
and we (instructor and I, or a bunch of us after a young eagles rally)
were usually the only traffic.

John