Author Topic: Flight Path And Related Issues  (Read 908773 times)

Offline Robert99

  • Hero Member
  • *****
  • Posts: 1711
  • Thanked: 196 times
Re: Flight Path And Related Issues
« Reply #2430 on: August 03, 2019, 02:27:48 PM »
You are not allowed to view links. Register or Login
This flight is entirely different from a basic everyday flight that is directed by controllers and not the pilots.

True again.
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2431 on: August 03, 2019, 02:58:54 PM »
You are not allowed to view links. Register or Login
Let's not lose sight of the fact that Ammerman stated that 305 was not on a prescribed flight path. He simply stated that to the best of his recollection 305 essentially stayed within V23--largely by default. Of course, the exception being the area west of PDX when he said it was near Hillsboro and probably a couple of miles outside of the western boundary for V23 proper. That said, 305 was heading to the Eugene VORTAC in a straight line so all was well.

That's interesting because in every interview Ive done with Cliff he insists - and is firm - 305 WAS NOT EVER a couple of miles outside of the western boundary for V23 proper - OR CLIFF WOULD HAVE BEEN ALARMED AND NOTIFIED HIM.

You did a good interview with Cliff but I sense you are now back to your games & claims, trying to prove a West Path because its crucial to your whole theory about the money.

Last night when this was fresh you said:

"I don’t think I need to explain what all of this means. That said, it is clear that this first-hand testimony from both Cliff and Catherine vindicates both R99 and me. Yes, it appears that R99 and I were wrong about the jet travelling from Toledo to Canby. Rather, it appears that 305 actually flew from east of Kelso to Eugene--remarkably, just west of both the Ridgefield National Wildlife Refuge and Tena Bar.

Today you are back to selling Jackalope meat! I knew you would be. And FLYJACK is in even deeper trying to sell phony doctored photos of the tie over at DZ, to Cooperland! It just never ends.

Could you and R99 give us a day to think etc ....... before stuffing more propaganda down our throats!? Trying to worm your way back in to your original claims? I mean push come to shove there are other ways of handling this he-said she-said Jesus in the Toast stuff.

Have a nice day. You earned it!  :rofl:     This may sound harsh or even like sour grapes, but I think its wise to hold back, before giving the whole farm away to the Elvis Impersonator ?

« Last Edit: August 03, 2019, 03:02:19 PM by georger »
 

Offline Robert99

  • Hero Member
  • *****
  • Posts: 1711
  • Thanked: 196 times
Re: Flight Path And Related Issues
« Reply #2432 on: August 03, 2019, 03:07:56 PM »
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
Quote
Cliff said today that as a general premise, 'everyone knew that something had happened during the 8:10-8:20 period' because of a sudden increase in communications, especially between 305 and the company.

Another suspicion I had concerning a lot of cross talk with the company and less with artcc allowing gaps in the radio transcripts..

V23 was discussed i believe with the tower and TRACON doesn't seem to be a part of this flight and would be the one's who would of noted the route taken.

Wouldnt Cliff have been party to those discussions or have heard them ?

Cliff is adamant that the PI and NWA Transcripts leave out vital communications that occurred with 305, especially during the 8:10-20 period. Cliff did not use the word "redactions" but when he got started on this part of our conversation I thought I was about to hear something straight out of R99's narrative - then Cliff switched to these comm gaps being due to 'transcribers being overwhelmed, or selective', or he said: "literally not knowing what to do with all of those communications" so sticking to a kind of script, for the intended user! Cliff's characterization surprised me. Ive never heard anyone offer that explanation before!

Finding EU's post here today ... it sounds like EU and I got our nickel's worth today from Mr. Ammerman. Cliff is a great gentleman.

Let me add some comments related to several posts.  Most of this information has been discussed before but some memories need to be refreshed.

While on the ground in Seattle, the airliner talked to the tower on the tower's ground control frequency.  It was cleared to take off on this ground control frequency and told to contact Seattle on a certain frequency.  When it called Seattle ATC, the answering controller was apparently surprised and had to ask them who they were and where they were.  That took a couple of minutes to get things straightened out.  This means that the airliner bypassed any TRACON (or tower and departure controller) controllers who were usually responsible for getting departing traffic into the ATC system.

Also while on the ground in Seattle, the airliner crew apparently was in communication on a radio link with the NWA ground personnel there.  This means that NWA apparently had its own private ground frequency in Seattle.  This was not part of the FAA system and would not be recorded or appear in the FAA radio transcripts.

The FAA tower frequencies and the Seattle ATC frequencies would be recorded on tape automatically.  Those tapes should still exist since they were part of an aircraft "incident".  Some human would then have to listen to those tapes and prepare a typed transcript of those conversations.  As previously discussed on my attempts to get those transcripts released, it is the FBI that prevents the FAA from releasing those tapes.  Three interventions by my US Representative and senior FBI managers were not able to get them released.  So it may take an intervention with the FBI Director and/or Supreme Court if we are ever able to get those complete and unredacted transcripts.

After take off, the airliner crew communicated with NWA personnel in Minneapolis and Seattle over the ARINC system by a voice patch as well as the usual teletype messages.  The voice patch was in real time and a few minutes later a "formatted" version of the same information would come through on the ARINC teletype system.  The air traffic controllers would not have access to that information.

A few years ago, Fred Poynter and his group at the WSHM were given access to the teletype version of those communications.  Fred's group made a study of them and determined that significant deletions had been made in those teletype messages.  That is, entire messages had been deleted.

Thanks to Cliff Ammerman for the information.  Does he know if Gerald H. Osterkamp is still alive?  If so, can Osterkamp be contacted.  He was the Chief of the Seattle ATC facility at the time of the hijacking.

I have still have some questions about the direct to Eugene flight path.  Hopefully, more information will be forthcoming.

Kermit!  Oh, Kermit!!!  You may need to have your medications adjusted.  ADDENDUM:  And based on his last post above, Georger may need to do  the same thing.
« Last Edit: August 03, 2019, 03:10:47 PM by Robert99 »
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2433 on: August 03, 2019, 03:14:38 PM »
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
Quote
Cliff said today that as a general premise, 'everyone knew that something had happened during the 8:10-8:20 period' because of a sudden increase in communications, especially between 305 and the company.

Another suspicion I had concerning a lot of cross talk with the company and less with artcc allowing gaps in the radio transcripts..

V23 was discussed i believe with the tower and TRACON doesn't seem to be a part of this flight and would be the one's who would of noted the route taken.

Wouldnt Cliff have been party to those discussions or have heard them ?

Cliff is adamant that the PI and NWA Transcripts leave out vital communications that occurred with 305, especially during the 8:10-20 period. Cliff did not use the word "redactions" but when he got started on this part of our conversation I thought I was about to hear something straight out of R99's narrative - then Cliff switched to these comm gaps being due to 'transcribers being overwhelmed, or selective', or he said: "literally not knowing what to do with all of those communications" so sticking to a kind of script, for the intended user! Cliff's characterization surprised me. Ive never heard anyone offer that explanation before!

Finding EU's post here today ... it sounds like EU and I got our nickel's worth today from Mr. Ammerman. Cliff is a great gentleman.

Let me add some comments related to several posts.  Most of this information has been discussed before but some memories need to be refreshed.

While on the ground in Seattle, the airliner talked to the tower on the tower's ground control frequency.  It was cleared to take off on this ground control frequency and told to contact Seattle on a certain frequency.  When it called Seattle ATC, the answering controller was apparently surprised and had to ask them who they were and where they were.  That took a couple of minutes to get things straightened out.  This means that the airliner bypassed any TRACON (or tower and departure controller) controllers who were usually responsible for getting departing traffic into the ATC system.

Also while on the ground in Seattle, the airliner crew apparently was in communication on a radio link with the NWA ground personnel there.  This means that NWA apparently had its own private ground frequency in Seattle.  This was not part of the FAA system and would not be recorded or appear in the FAA radio transcripts.

The FAA tower frequencies and the Seattle ATC frequencies would be recorded on tape automatically.  Those tapes should still exist since they were part of an aircraft "incident".  Some human would then have to listen to those tapes and prepare a typed transcript of those conversations.  As previously discussed on my attempts to get those transcripts released, it is the FBI that prevents the FAA from releasing those tapes.  Three interventions by my US Representative and senior FBI managers were not able to get them released.  So it may take an intervention with the FBI Director and/or Supreme Court if we are ever able to get those complete and unredacted transcripts.

After take off, the airliner crew communicated with NWA personnel in Minneapolis and Seattle over the ARINC system by a voice patch as well as the usual teletype messages.  The voice patch was in real time and a few minutes later a "formatted" version of the same information would come through on the ARINC teletype system.  The air traffic controllers would not have access to that information.

A few years ago, Fred Poynter and his group at the WSHM were given access to the teletype version of those communications.  Fred's group made a study of them and determined that significant deletions had been made in those teletype messages.  That is, entire messages had been deleted.

Thanks to Cliff Ammerman for the information.  Does he know if Gerald H. Osterkamp is still alive?  If so, can Osterkamp be contacted.  He was the Chief of the Seattle ATC facility at the time of the hijacking.

I have still have some questions about the direct to Eugene flight path.  Hopefully, more information will be forthcoming.

Kermit!  Oh, Kermit!!!  You may need to have your medications adjusted.  ADDENDUM:  And based on his last post above, Georger may need to do  the same thing.


Kermit!  Oh, Kermit!!!  You may need to have your medications adjusted.

Really?

Why blemish a very fine statement above with this? Don't feel guilty for making a fine post!  :rofl:

 

Offline Robert99

  • Hero Member
  • *****
  • Posts: 1711
  • Thanked: 196 times
Re: Flight Path And Related Issues
« Reply #2434 on: August 03, 2019, 03:16:40 PM »
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
Quote
Cliff said today that as a general premise, 'everyone knew that something had happened during the 8:10-8:20 period' because of a sudden increase in communications, especially between 305 and the company.

Another suspicion I had concerning a lot of cross talk with the company and less with artcc allowing gaps in the radio transcripts..

V23 was discussed i believe with the tower and TRACON doesn't seem to be a part of this flight and would be the one's who would of noted the route taken.

Wouldnt Cliff have been party to those discussions or have heard them ?

Cliff is adamant that the PI and NWA Transcripts leave out vital communications that occurred with 305, especially during the 8:10-20 period. Cliff did not use the word "redactions" but when he got started on this part of our conversation I thought I was about to hear something straight out of R99's narrative - then Cliff switched to these comm gaps being due to 'transcribers being overwhelmed, or selective', or he said: "literally not knowing what to do with all of those communications" so sticking to a kind of script, for the intended user! Cliff's characterization surprised me. Ive never heard anyone offer that explanation before!

Finding EU's post here today ... it sounds like EU and I got our nickel's worth today from Mr. Ammerman. Cliff is a great gentleman.

Let me add some comments related to several posts.  Most of this information has been discussed before but some memories need to be refreshed.

While on the ground in Seattle, the airliner talked to the tower on the tower's ground control frequency.  It was cleared to take off on this ground control frequency and told to contact Seattle on a certain frequency.  When it called Seattle ATC, the answering controller was apparently surprised and had to ask them who they were and where they were.  That took a couple of minutes to get things straightened out.  This means that the airliner bypassed any TRACON (or tower and departure controller) controllers who were usually responsible for getting departing traffic into the ATC system.

Also while on the ground in Seattle, the airliner crew apparently was in communication on a radio link with the NWA ground personnel there.  This means that NWA apparently had its own private ground frequency in Seattle.  This was not part of the FAA system and would not be recorded or appear in the FAA radio transcripts.

The FAA tower frequencies and the Seattle ATC frequencies would be recorded on tape automatically.  Those tapes should still exist since they were part of an aircraft "incident".  Some human would then have to listen to those tapes and prepare a typed transcript of those conversations.  As previously discussed on my attempts to get those transcripts released, it is the FBI that prevents the FAA from releasing those tapes.  Three interventions by my US Representative and senior FBI managers were not able to get them released.  So it may take an intervention with the FBI Director and/or Supreme Court if we are ever able to get those complete and unredacted transcripts.

After take off, the airliner crew communicated with NWA personnel in Minneapolis and Seattle over the ARINC system by a voice patch as well as the usual teletype messages.  The voice patch was in real time and a few minutes later a "formatted" version of the same information would come through on the ARINC teletype system.  The air traffic controllers would not have access to that information.

A few years ago, Fred Poynter and his group at the WSHM were given access to the teletype version of those communications.  Fred's group made a study of them and determined that significant deletions had been made in those teletype messages.  That is, entire messages had been deleted.

Thanks to Cliff Ammerman for the information.  Does he know if Gerald H. Osterkamp is still alive?  If so, can Osterkamp be contacted.  He was the Chief of the Seattle ATC facility at the time of the hijacking.

I have still have some questions about the direct to Eugene flight path.  Hopefully, more information will be forthcoming.



Kermit!  Oh, Kermit!!!  You may need to have your medications adjusted.

Really?

Why blemish a very fine statement above with this? Don't feel guilty for making a fine post!  :rofl:

Okay, I deleted it.
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2435 on: August 03, 2019, 03:22:22 PM »
R99 says:

Let me add some comments related to several posts.  Most of this information has been discussed before but some memories need to be refreshed.

While on the ground in Seattle, the airliner talked to the tower on the tower's ground control frequency.  It was cleared to take off on this ground control frequency and told to contact Seattle on a certain frequency.  When it called Seattle ATC, the answering controller was apparently surprised and had to ask them who they were and where they were.  That took a couple of minutes to get things straightened out.  This means that the airliner bypassed any TRACON (or tower and departure controller) controllers who were usually responsible for getting departing traffic into the ATC system.

Also while on the ground in Seattle, the airliner crew apparently was in communication on a radio link with the NWA ground personnel there.  This means that NWA apparently had its own private ground frequency in Seattle.  This was not part of the FAA system and would not be recorded or appear in the FAA radio transcripts.

The FAA tower frequencies and the Seattle ATC frequencies would be recorded on tape automatically.  Those tapes should still exist since they were part of an aircraft "incident".  Some human would then have to listen to those tapes and prepare a typed transcript of those conversations.  As previously discussed on my attempts to get those transcripts released, it is the FBI that prevents the FAA from releasing those tapes.  Three interventions by my US Representative and senior FBI managers were not able to get them released.  So it may take an intervention with the FBI Director and/or Supreme Court if we are ever able to get those complete and unredacted transcripts.

After take off, the airliner crew communicated with NWA personnel in Minneapolis and Seattle over the ARINC system by a voice patch as well as the usual teletype messages.  The voice patch was in real time and a few minutes later a "formatted" version of the same information would come through on the ARINC teletype system.  The air traffic controllers would not have access to that information.

A few years ago, Fred Poynter and his group at the WSHM were given access to the teletype version of those communications.  Fred's group made a study of them and determined that significant deletions had been made in those teletype messages.  That is, entire messages had been deleted.

Thanks to Cliff Ammerman for the information.  Does he know if Gerald H. Osterkamp is still alive?  If so, can Osterkamp be contacted.  He was the Chief of the Seattle ATC facility at the time of the hijacking.

I have still have some questions about the direct to Eugene flight path.  Hopefully, more information will be forthcoming.


reply:

Cliff stressed that these communications are vital to understanding where Cooper bailed and when.







 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2436 on: August 03, 2019, 03:28:06 PM »
Quote
That's interesting because in every interview Ive done with Cliff he insists - and is firm - 305 WAS NOT EVER a couple of miles outside of the western boundary for V23 proper - OR CLIFF WOULD HAVE BEEN ALARMED AND NOTIFIED HIM.

Based on looking at the map and statements from radar operators as well as pilots the plane was on the east side of V23 from Toledo to nearing the Columbia river. it's the totality one needs to look at that bring things together. if we had conflicting statements with the totality it would then raise questions. I fail to see any to date.
« Last Edit: August 03, 2019, 03:28:49 PM by Shutter »
 

Offline EU

  • Hero Member
  • *****
  • Posts: 1759
  • Thanked: 322 times
    • ERIC ULIS: From the History Channel
Re: Flight Path And Related Issues
« Reply #2437 on: August 03, 2019, 04:17:20 PM »
GEORGER:

Let me be absolutely clear. What I conveyed Cliff told me is precisely the truth. This includes that he estimates the jet traveled very near Hillsboro.

Don't ever libel me again. Call Cliff yourself to verify. Then report back with an apology.
Some men see things as they are, and ask why? I dream of things that never were, and ask why not?

RFK
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2438 on: August 03, 2019, 04:59:55 PM »
According to the flight path and the eastern edge of Hillsboro would be less than 10 miles. this could very well be considered "very close" I seriously doubt Portland would of missed the plane if you wish to place it further west to line up with the Columbia. it appears were are going right back to where it started...
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2439 on: August 03, 2019, 05:19:17 PM »
Quote
Cliff told me that 305 made the turn at Toledo and started heading toward the Battlefield VORTAC. He said 305 was likely west of the V23 centerline at this point. He then stated that at an estimated point east of Kelso that 305 modified its heading by an estimated 15 degrees to the west. He stated this was done so that 305 would pass west of Vancouver and Portland and cutout the “dogleg” in the V23 flight path. He said that 305 headed directly for the Eugene VORTAC from this point east of Kelso.

30 miles between Kelso and Battleground. why would he reference so far apart. we have established the plane turned at Toledo vs flying past it from malay. now it's heading towards Battleground which once again is consistent with the map. the Kelso area is around the 20:05 location where a westerly jog can be noted. going straight down from east of Kelso would place the plane miles from where other operators close to the plane mark it's location and make there statements of never leaving V23 false.

I can't go back and forth with this again. for that reason. I'm out. we are right back to everything being wrong.

 

Offline EU

  • Hero Member
  • *****
  • Posts: 1759
  • Thanked: 322 times
    • ERIC ULIS: From the History Channel
Re: Flight Path And Related Issues
« Reply #2440 on: August 03, 2019, 05:44:08 PM »
All I can tell you is what Cliff said. Consider that the location comments aren't meant to convey precise data. Rather, Cliff gave me his estimates of where the jet was at certain times. What was abundantly clear in any case is the belief on the part of him and Captain Scott's friend Catherine that 305 traveled west of downtown Portland and that this was done intentionally. Moreover, Cliff made it clear he cannot explain the FBI map denoting erratic turns left and right because he stated that the T-33 received only one vector all the way down to Eugene. Simply put, both 305 and the T-33 flew in a straight line to Eugene from a point approximately east of Kelso.
Some men see things as they are, and ask why? I dream of things that never were, and ask why not?

RFK
 

Offline Robert99

  • Hero Member
  • *****
  • Posts: 1711
  • Thanked: 196 times
Re: Flight Path And Related Issues
« Reply #2441 on: August 03, 2019, 05:51:13 PM »
You are not allowed to view links. Register or Login
All I can tell you is what Cliff said. Consider that the location comments aren't meant to convey precise data. Rather, Cliff gave me his estimates of where the jet was at certain times. What was abundantly clear in any case is the belief on the part of him and Captain Scott's friend Catherine that 305 traveled west of downtown Portland and that this was done intentionally. Moreover, Cliff made it clear he cannot explain the FBI map denoting erratic turns left and right because he stated that the T-33 received only one vector all the way down to Eugene. Simply put, both 305 and the T-33 flew in a straight line to Eugene from a point approximately east of Kelso.

As I pointed out last night on another EU post, what EU has posted is consistent with the facts as they are understood at this time.  I'm sure that some refinements to this can be made as more accurate information becomes available but the basic facts given above by EU are going to stand.
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2442 on: August 04, 2019, 12:19:53 AM »
You are not allowed to view links. Register or Login
All I can tell you is what Cliff said. Consider that the location comments aren't meant to convey precise data. Rather, Cliff gave me his estimates of where the jet was at certain times. What was abundantly clear in any case is the belief on the part of him and Captain Scott's friend Catherine that 305 traveled west of downtown Portland and that this was done intentionally. Moreover, Cliff made it clear he cannot explain the FBI map denoting erratic turns left and right because he stated that the T-33 received only one vector all the way down to Eugene. Simply put, both 305 and the T-33 flew in a straight line to Eugene from a point approximately east of Kelso.

because he stated that the T-33 received only one vector all the way down to Eugene

You mean one instruction to 'vector' ,   'make a turn' ?   Or do you mean Victor not Vector?

What are you saying?


* The T33 took off from PDX and went west then north, then was turned by Cliff to come in behind 305 ... all of this NORTH of the Columbia BEFORE 305 even crossed the Columbia, according to Cliff. So what is this 'vectoring' you are talking about? 
« Last Edit: August 04, 2019, 12:25:36 AM by georger »
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2443 on: August 04, 2019, 12:27:13 AM »
It appears everyone followed like a row of ducks or a perfect GPS route. If Ammerman knew they were on v23 he would of directed the chase plane to the same. how this deletes turns or deviations inside a corridor is yet to be explained. we are close to breaching another airway west of the Columbia using Kelso to Eugene in a straight line.

If Ammerman was handed the flight around Toledo he wasn't R2. he would be R5 I think is the next controller.
 

Offline EU

  • Hero Member
  • *****
  • Posts: 1759
  • Thanked: 322 times
    • ERIC ULIS: From the History Channel
Re: Flight Path And Related Issues
« Reply #2444 on: August 04, 2019, 12:27:30 AM »
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
All I can tell you is what Cliff said. Consider that the location comments aren't meant to convey precise data. Rather, Cliff gave me his estimates of where the jet was at certain times. What was abundantly clear in any case is the belief on the part of him and Captain Scott's friend Catherine that 305 traveled west of downtown Portland and that this was done intentionally. Moreover, Cliff made it clear he cannot explain the FBI map denoting erratic turns left and right because he stated that the T-33 received only one vector all the way down to Eugene. Simply put, both 305 and the T-33 flew in a straight line to Eugene from a point approximately east of Kelso.

because he stated that the T-33 received only one vector all the way down to Eugene

You mean one instruction to 'vector' ,   'make a turn' ?   Or do you mean Victor not Vector?

What are you saying?

My verbiage may or may not be incorrect.

Regardless, when the T-33 was pulled in five miles behind 305 he was given a specific heading that was the same as 305. This heading was never changed. The T-33 and 305 flew in a straight line all the way to Eugene. This according to Cliff.
Some men see things as they are, and ask why? I dream of things that never were, and ask why not?

RFK