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.

This link was not found. (404 error).

Got an alternate link to it?

Chris G.

john smith wrote:
00:01:15 minutes into the playback is when the accident occurred on 23
July

http://www.liveatc.net/.archive/kosh...2006-1330Z.mp3

"Chris G." wrote:

This link was not found. (404 error).

Got an alternate link to it?

LiveATC's archive server is down for the next few days due to a major
upgrade. Hopefully the archive files from these dates will be preserved
when the new server goes online.

Check back later in the week, or perhaps over the weekend.

--
Peter

"Chris G." wrote:

This link was not found. (404 error).

Got an alternate link to it?

On second thought, Chris, someone posted an edited version of this clip
over in the LiveATC audio clip forum. I grabbed the clip and uploaded it
to Spread-it.com. This link will be available for two weeks from today
(Spread-it's hosting policy).

http://www5.spread-it.com/dl.php?id=...ec1f3432436b10

As was pointed out earlier in this thread, this is not sensationalistic
audio of the pilot's final words, but rather a testament to the
professionalism of the ATC during that tragedy.


--
Peter

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...

In article ,
Jose wrote:

The way I read it, "Free" means "available". "Mind capacity" means
"ability to think". We sometimes refer to it as "processor cycles", by
anaolgy to computing. When one is thinking too much, there is not much
mind capacity left for other tasks, so there is not much "free" mind
capactity, although one's total mind capacity ("intellegence") is unaltered.

For MicroSoft Windows users, this would be a buffer overrun error. It's
a common hacker technique to take control of someone else's computer.

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."

"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

In article ,
"RST Engineering" wrote:

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."

Good catch, Jim. I think there should be something to dissuade people
from holding, though. It leads to the problems we witnessed this year
and creates a false impression that the airport will be opening soon.

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)