A aviation & planes forum. AviationBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Piloting
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

23 July OSH accident audio



 
 
Thread Tools Display Modes
  #1  
Old August 1st 06, 03:37 PM posted to rec.aviation.piloting
Thomas Borchert
external usenet poster
 
Posts: 1,749
Default 23 July OSH accident audio

Steven,

"Hold there because of an accident" provides an idea of how long the delay
will be


How long will it be? I seriously want to know.

--
Thomas Borchert (EDDH)

  #2  
Old August 1st 06, 04:46 PM posted to rec.aviation.piloting
Morgans[_3_]
external usenet poster
 
Posts: 407
Default 23 July OSH accident audio

How long will it be? I seriously want to know.

Minimum for a collapsed gear, 30 minutes, fatal acciden t60 - 90 minutes,
would be close.
--
Jim in NC

  #3  
Old August 1st 06, 04:51 PM posted to rec.aviation.piloting
Thomas Borchert
external usenet poster
 
Posts: 1,749
Default 23 July OSH accident audio

Morgans,

Minimum for a collapsed gear, 30 minutes, fatal acciden t60 - 90 minutes,
would be close.


So if a controller says "delay due to accident", you have a 300 percent
error margin, with 30 minutes probably being sensible to wait out and 90
minutes being a little on the long side. I wouldn't know what to do with
that information, but, well, that's just me.

--
Thomas Borchert (EDDH)

  #4  
Old August 1st 06, 05:13 PM posted to rec.aviation.piloting
Steven P. McNicoll[_1_]
external usenet poster
 
Posts: 660
Default 23 July OSH accident audio


"Thomas Borchert" wrote in message
...

So if a controller says "delay due to accident", you have a 300 percent
error margin, with 30 minutes probably being sensible to wait out and 90
minutes being a little on the long side. I wouldn't know what to do with
that information, but, well, that's just me.


So it appears.


  #5  
Old August 1st 06, 07:32 PM posted to rec.aviation.piloting
Grumman-581[_1_]
external usenet poster
 
Posts: 491
Default 23 July OSH accident audio

On Tue, 01 Aug 2006 17:51:42 +0200, Thomas Borchert
wrote:
So if a controller says "delay due to accident", you have a 300 percent
error margin, with 30 minutes probably being sensible to wait out and 90
minutes being a little on the long side. I wouldn't know what to do with
that information, but, well, that's just me.


When I flew to OSH back in 2002, I had refueled at Kirksvill, MO (IRK)
and as such, I had at least 2 hours of fuel, just in case there was
any sort of delay... I can see how someone with less of a fuel reserve
might start getting a bit testy with the prospect of an indeterminate
delay...
  #6  
Old August 2nd 06, 08:58 AM posted to rec.aviation.piloting
Thomas Borchert
external usenet poster
 
Posts: 1,749
Default 23 July OSH accident audio

Grumman-581,

. I can see how someone with less of a fuel reserve
might start getting a bit testy with the prospect of an indeterminate
delay...


So, accident or not, they leave...

--
Thomas Borchert (EDDH)

  #7  
Old August 1st 06, 04:09 PM posted to rec.aviation.piloting
Steven P. McNicoll[_1_]
external usenet poster
 
Posts: 660
Default 23 July OSH accident audio


"Thomas Borchert" wrote in message
...

Steven,

"Hold there because of an accident" provides an idea of how long the
delay
will be


How long will it be? I seriously want to know.


One hour minimum.


  #8  
Old August 1st 06, 05:02 PM posted to rec.aviation.piloting
RST Engineering
external usenet poster
 
Posts: 1,147
Default 23 July OSH accident audio

And I choose to take that 1 to 3 hour wait back at Portage, where I can have
a couple of more morning brats, listen to 120.7 for the chatter to start
back up, fill up the tanks, and relax.

As for not announcing that the incident/accident was fatal, not a problem.
Simply say "accident" and be done with it. Now we know it isn't airport
overload.

Oshkosh and "gottagetthere" don't belong in the same sentence.

Jim



"Steven P. McNicoll" wrote in message
nk.net...


One hour minimum.



  #9  
Old August 2nd 06, 12:11 AM posted to rec.aviation.piloting
john smith
external usenet poster
 
Posts: 1,446
Default 23 July OSH accident audio

In article ,
"RST Engineering" wrote:

As for not announcing that the incident/accident was fatal, not a problem.
Simply say "accident" and be done with it. Now we know it isn't airport
overload.


How about this:
on ATIS: "Oshkosh Airport is closed indefinitely. All aircraft are
advised to land at other airports. A NOTAM stating the airport closure
has been issued. When the airport is re-opened, the NOTAM will be
cancelled. The RIPON Arrival Procedure will remain in effect following
the reopening of the airport."

FISKE Controllers: "Oshkosh Airport is closed. Any aircraft inbound on
the RIPON Arrival Procedure are instructed to land at another airport
until the Oshkosh Airport reopens. Any aircraft proceeding beyond FISKE
will not be allowed to land at Oshkosh."

OSH Tower: "The Oshkosh Airport is closed indefinitely. Any aircraft
landing while the airport is closed will be subject to FAA enforcement
actions. You are instructed to depart the Oshkosh Class D Airspace and
remain clear. A NOTAM advising of the airport closure has been issued.
It is recommended that all aircraft desiring to land Oshkosh divert to
an outlying airport and monitor the NOTAM for cancellation and reopening
of the Oshkosh Airport."
  #10  
Old August 2nd 06, 12:24 AM posted to rec.aviation.piloting
RST Engineering
external usenet poster
 
Posts: 1,147
Default 23 July OSH accident audio


"john smith" wrote in message
...
In article ,
"RST Engineering" wrote:

As for not announcing that the incident/accident was fatal, not a
problem.
Simply say "accident" and be done with it. Now we know it isn't airport
overload.



FISKE Controllers: "Oshkosh Airport is closed. Any aircraft inbound on
the RIPON Arrival Procedure are instructed to land at another airport
until the Oshkosh Airport reopens. Any aircraft proceeding beyond FISKE
will not be allowed to land at Oshkosh."


I disagree with this one. If you don't go to another airport, you are
disobeying a direct order from ATC. I prefer to give the pilot the option
of the Rush Lake hold, the Green Lake hold, or diversion at the pilot's
option. All questions of the nature "how long will the hold be" are
answered the same way, "the hold is indefinite ... there has been an
accident at Oshkosh airport."

THe procedure is Fisk, not FISKE.

And I'd have Fisk ask the first ten or twenty aircraft in the ensuing open
field lineup to say words on the aircraft's radio that the field is open.
THat way those who have diverted and are listening on a handheld below the
ATIS line of sight will have a clue that the airport has reopened. Line of
sight (radio horizon) for an aircraft at 1000 AGL is about 45 miles.

Jim

Jim


 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Air Force One Had to Intercept Some Inadvertent Flyers / How? Rick Umali Piloting 29 February 15th 06 04:40 AM
I want to build the most EVIL plane EVER !!! Eliot Coweye Home Built 237 February 13th 06 03:55 AM
Most reliable homebuilt helicopter? tom pettit Home Built 35 September 29th 05 02:24 PM
Mini-500 Accident Analysis Dennis Fetters Rotorcraft 16 September 3rd 05 11:35 AM
Nearly had my life terminated today Michelle P Piloting 11 September 3rd 05 02:37 AM


All times are GMT +1. The time now is 09:41 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 AviationBanter.
The comments are property of their posters.