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

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2415 on: August 02, 2019, 11:00:50 PM »
Flying directly to Newburg VOR would deviate from V23 putting them on what appears to be V33 which is 9NM from V23.
 

Offline Robert99

  • Hero Member
  • *****
  • Posts: 1711
  • Thanked: 196 times
Re: Flight Path And Related Issues
« Reply #2416 on: August 02, 2019, 11:29:21 PM »
You are not allowed to view links. Register or Login
Flying directly to Newburg VOR would deviate from V23 putting them on what appears to be V33 which is 9NM from V23.

I don't see a V-33 at Newberg.  There is a V-23W there and there is a V-23E which is east of V-23. 
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2417 on: August 02, 2019, 11:49:31 PM »
Interesting....looking at my sectional map from that era it appears there was 3 V23's...the one going to Newburg is at 194 degree's and considered west while the one going directly through PDX is at 160 degree's is considered east. the airway in the center at 175 degree's in the one where the path is plotted and not known as east or west...I was looking at an online map that has the first portion distorted. this would still be a change in airways...
« Last Edit: August 03, 2019, 12:04:20 AM by Shutter »
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2418 on: August 03, 2019, 12:29:33 AM »
You are not allowed to view links. Register or Login
It appears that some news is about to break so I will let you all in on what I have learned in some discussions I’ve had with Cliff Ammerman recently. I have been sitting on this information but decided to go forward with its release now that it appears others have recently reached out to Cliff.

Cliff was controlling the airspace in Sector 4 and Sector 5 on November 24, 1971. He was handed 305 about 10 miles north of Toledo as it entered Sector 4. He explained that this was somewhat complicated by the fact that the controller in Sector 2 attempted to hand 305 off to the controller handling Sector 4 traffic for the higher altitude which would have been normal. However, given that 305 stayed at 10,000 feet it was actually Cliff who would be handling the flight.

Cliff stated that this also explains why the transcripts are missing data. Specifically, he said that when they were transcribed it appears that the person doing the transcription was listening to the tapes from the controller handling the higher altitude of Sector 4 and not the altitude that Cliff was covering and that 305 was actually flying in.

Cliff was located in Auburn. He took over 305 and communicated with the pilots of 305 briefly as the hand off was effected. In addition, Cliff also took over duties for the two F-106 fighters as they entered Sector 4.

Cliff stated that 305 did not have a prescribed flight path. Therefore, his job was to keep an eye on 305 and make certain that no other aircraft got near 305. Also he was tasked with directing the F-106s.

The F-106s never made visual contact with 305. In fact, they trailed at five miles behind from 11,000 feet. Moreover, the F-106s were having a problem flying at such slow speeds. Therefore, they would have to make some S turns occasionally. Cliff explained that the F-106 has onboard radar that enables them to see targets 10 degrees to the left and right for a total scan range of only 20 degrees. This means that as the jets would make their S turns they would lose contact with 305 on radar but regain contact once they came back around.

Not too long after Cliff took over 305 and the F-106s a single T-33 took off from PDX. Cliff directed the T-33 west then north to meet 305. At a point approximately 10 miles north of PDX Cliff had the T-33 swing around in behind 305. The T-33 was placed five miles behind at 11,000 feet. The T-33 never made visual contact with 305.

At this point Cliff directed the F-106s to an altitude of 20,000 feet and 10 miles east of 305. Then all four jets continued south.

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.

Cliff also stated that when the T-33 pulled in behind 305 shortly after the new Kelso heading that he gave the T-33 a heading consistent with 305 and that he never modified that heading. In other words, 305 and the T-33 flew in a straight line to the Eugene VORTAC.

Cliff stated that one matter to consider is that an airliner flying at a normal altitude of 33,000 feet would have no trouble seeing VORTACs a great distance away. However, given that 305 was travelling only at 10,000 feet and the weather was murky that this would inhibit the range of VORTAC detection.

He stated that 305 largely stayed within V23 which is 10 miles wide. However, he stated that he believed it flew outside of the western boundary by a small amount (a couple of miles) as the jet was west of PDX. He further stated this was not a concern and that often the navigation of airplanes will differ by a couple of miles from their screens at air traffic control so it isn’t an issue if a jet flies a little out of a set vector. Nonetheless, 305 was not set to stay within V23 anyway so it didn’t matter. Cliff stated that he estimates that 305 travelled near Hillsboro during that part of the flight.

Cliff also mentioned that airliners communicate using VHF and the military uses UHF. However, the switches are toggled so that he can broadcast to both the airliner and the military at the same time. But, they were concerned that Cooper would be able to hear their communication with the military jets. Therefore, he would stand up and un-toggle the switches so he could communicate with the military jets privately. He mentioned that this was labor intensive so at a point somewhere around Kelso or south of Kelso he had 305 switch over to another frequency. Apparently they had a radio tower on Sauvie Island. The other frequency meant that 305 would be communicating with the controller handling the Sector 4 airspace at the lower level—9,000 feet to ground level—even though 305 was flying at 10,000 feet.

Just south of Portland 305 entered Sector 5 which went all the way to Eugene. Cliff was also handling traffic in Sector 5.

Cliff said that as the jets were travelling in a straight line toward the Eugene VORTAC south of Portland that they naturally were merging closer to the V23 center line. He added that as the group was approaching Eugene that the T-33 was getting low on fuel and was turned back to PDX. Also at this time the F-106s stated that they didn’t have that much fuel to continue on much longer so they suggested that they use this opportunity to send the F-106s back to McChord which was done.

Importantly, as I interviewed Cliff I did not tell him of my thoughts regarding the Western Flight Path. I asked him to tell me what happened that night. Moreover, in a later phone call when I explained the FBI flight path he said he was completely unaware of it. In other words, he had no idea that his thoughts about the flight path and the jet flying west of Portland contradicted the FBI’s version of the flight path.

Also, he stated that the FBI never interviewed him. Additionally, he was unaware of the FBI interviewing any of the air traffic controllers in his group.

Finally, Cliff told me that he knows a former Northwest Orient flight attendant named Catherine. This woman was not on 305. However, she knew Captain Scott personally. Catherine stated that Captain Scott told her in later years that he purposely flew the jet west of Portland because he was concerned about the prospect of a bomb being on the jet and the safety of those on the ground.

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.

Those, ladies and gentleman, are the facts.

What a coincidence! Having talked to Cliff today I concur with much of what you say. You touched points with Cliff I talked with Cliff about today. Several differences however, which Cliff brought up today and made more comments I may post about later.

1. Cliff has had the FBI flight path map (hi res version) and all Transcripts I have (PI, NWA, etc) since 2010, because I sent them to him.

2, He seemed anxious to talk about the transcripts today, perhaps because he has just talked about them with you? He basically told me the same things you relate him saying - but he said he attributes blanks in the transcripts which convey military and NWA communications to the 'transcriber not knowing what to do with them'! Cliff asked me if I had ever seen NWA's company comm notes? He said 'I would love to see those'. I told him so far as I knew nobody has ever seen those transcriptions. I told him I asked Bruce Kitt several times about those transcriptions and Kitt surprised me saying he had asked for them but could never get them released. Cliff is firm that all of the tapes and transcriptions from the Cooper case still exist and are being held by the FAA.

3. 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. He said 'none of those communications are reflected in any Transcript, and I noticed this immediately after you sent me those transcripts'. Cliff believes the 305/NWA communications are vital to understanding what happened and when, and where. Cliff said, 'the transcripts show the exact opposite, a total gap in communications for that same period. Just the opposite was the case'.

4. Cliff said today that the T33 intercepted and was trailing 305 before 305 even crossed the Columbia. river. The previous intercept at Lake Oswego story is now null and void! 

5. Cliff said 305 was never assigned to V23. He said today as time passed it appeared 305 was staying within V23, but as far as he knows 305 was never assigned to V23 or told it had to stay within V23. As 305 progressed south it appeared the pilot had chosen V23, so Cliff says 'there came a point where if 305 had left V23' I would have immediately advised the pilot he was now outside of V23, just as a precaution. He says that never happened during the period he was in charge of 305. 

Let me end this hear. My concern now is a 'he said vs she said' situation with EU. Let me digest what EU has said above. I generally try to avoid traffic jams!
« Last Edit: August 03, 2019, 12:48:07 AM by georger »
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2419 on: August 03, 2019, 12:44:46 AM »
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.
« Last Edit: August 03, 2019, 12:47:05 AM by Shutter »
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2420 on: August 03, 2019, 12:57:53 AM »
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.
« Last Edit: August 03, 2019, 01:03:33 AM by georger »
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2421 on: August 03, 2019, 01:05:37 AM »
I don't think any of the controllers would hear anything from the company. we read this on the transcripts "sorry, was talking to the company" I believe it was a phone patch?
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2422 on: August 03, 2019, 01:08:58 AM »
I believe the transcripts state the tower asking that nobody transmit on the frequency? I'm not sold anything was left out for reasons of covering up or hiding any location.
« Last Edit: August 03, 2019, 01:09:55 AM by Shutter »
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2423 on: August 03, 2019, 01:09:32 AM »
You are not allowed to view links. Register or Login
I don't think any of the controllers would hear anything from the company. we read this on the transcripts "sorry, was talking to the company" I believe it was a phone patch?

That's what Cliff says. I asked him about that several times today.

Been a busy day!  :rofl:  I am going over to the tie issue FJ raised to day ... maybe see you there too..
 

Offline Robert99

  • Hero Member
  • *****
  • Posts: 1711
  • Thanked: 196 times
Re: Flight Path And Related Issues
« Reply #2424 on: August 03, 2019, 01:56:56 PM »
You are not allowed to view links. Register or Login
Interesting....looking at my sectional map from that era it appears there was 3 V23's...the one going to Newburg is at 194 degree's and considered west while the one going directly through PDX is at 160 degree's is considered east. the airway in the center at 175 degree's in the one where the path is plotted and not known as east or west...I was looking at an online map that has the first portion distorted. this would still be a change in airways...

As has been discussed previously, a number of airways and navigational facilities in the Portland/Seattle area have been renamed since 1971.  Mayfield Intersection is now named Malay Intersection.  Portland VORTAC is now named Battleground VORTAC.  V-23E between Portland/Seattle and other points is now named V-495.  Other names have been changed also.
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2425 on: August 03, 2019, 01:58:42 PM »
Still no reference to changing airways no matter the changing of the name..
 

Offline EU

  • Hero Member
  • *****
  • Posts: 1759
  • Thanked: 322 times
    • ERIC ULIS: From the History Channel
Re: Flight Path And Related Issues
« Reply #2426 on: August 03, 2019, 02:13:09 PM »
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.
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 #2427 on: August 03, 2019, 02:17:23 PM »
You are not allowed to view links. Register or Login
Still no reference to changing airways no matter the changing of the name..

True.
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2428 on: August 03, 2019, 02:18:32 PM »
The map pretty much shows a straight line to Eugene. just as it shows it within the limits of V23. is the map perfect, no. is it close. more than likely. IMO, it would be pretty simple to line up the FDR with the map. the turns didn't come out of thin air. the reasoning is uncertain more than unlikely.
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2429 on: August 03, 2019, 02:20:19 PM »
This flight is entirely different from a basic everyday flight that is directed by controllers and not the pilots.