View Single Post
  #4  
Old August 17th 05, 06:53 PM
Steven P. McNicoll
external usenet poster
 
Posts: n/a
Default


"Mike Weller" wrote in message
news:1124291160.a4b773a96257a25b104a0209edc5c8ac@o nlynews...

Boy, I just checked my log book. I landed at Sarasota Florida on
runway 14 on March 10, 2000 on top of a black spot on the runway.

An honest-to-God FAA controller had cleared a plane for position and
hold and at the same time cleared another airplane to take off.


I'm familiar with this incident. The local controller believed the Skyhawk
was departing full length because strip marking indicated that's where he
was and there was a Skyhawk in that position. The Skyhawk pilot did not
properly identify his position as being at an intersection downfield.



They hit at the intersection where the first plane was in position and
hold. The plane that hit them was an instructor with a student pilot.

For the life of me, I can't see why it happened, but the plane that
was in position and hold never had a chance to see the plane that ran
into them.


Did you not read the report? Did the aircraft departing full length have a
chance to see the plane downfield? Why did the Skyhawk pilot not hear the
takeoff clearance issued to the full length departure?



So what is so honest-to-God bad about not lining up perfectly on the
runway instead of stopping a little bit crossways to watch what is
happening on the runway?


How far off the runway alignment would a Skyhawk at an intersection need to
be in order to have an unobstructed view?



And don't give me any excuses about one of the aircraft not obeying
ATC instructions. Neither plane did anything against ATC
instructions. Read the NTSB report. It was a human error on the part
of the controller.


Errors were made by the ground controller and the Skyhawk pilot, but not by
the local controller.

So, what ****ed you off?