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

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2370 on: July 30, 2019, 02:53:11 PM »
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
On another note, Cliff stresses throughout these interviews how very important it was that 305 be kept within V23 (and as close to the center line as possible), precisely because of the chase plane intercepts and trailing that Cliff says began at the Toledo intersection, which he had to personally manage. He says things got hectic when he had to bring the T33 in, in addition to the F-106s covering with their narrow radar cones, crossing on the west side of PDX ...

Let me add some information that Georger passed to me about 10 years ago.  He said that he had talked to a number of people who ran the airports on the east side of Portland and not a single one of them indicated that the airliner passed on the east side.  All of them indicated that it bypassed Portland on the west side.

In addition to the information from Georger, I have never seen any credible information from other sources that disagreed with the airliner bypassing Portland on the west side.  And there are a number of actual facts, not opinions, that strongly support the west side bypass.

I told Cliff about JT's claim that 305 had passed over the Troutdale airport. Cliff laughed and said "WHO SAYS THAT!" I explained it again and added Himmelsbach's name. Cliff says "That is nonsense - never happened". In fact Cliff's reaction was so strong I thought I was going to lose him on the telephone, until I interrupted and told him I had talked to the Manager of the Troutdale airport who was present on the evening of the hijacking, who laughed at JT's claim. Cliff's reaction in this exchange clued me into just how seriously he takes these matters! He said: 'its xxxx like that that makes me reluctant to give interviews at all .........'

I thought to myself in that moment: 'the east path is dead'! 
 

Offline Robert99

  • Hero Member
  • *****
  • Posts: 1711
  • Thanked: 196 times
Re: Flight Path And Related Issues
« Reply #2371 on: July 30, 2019, 02:55:44 PM »
You are not allowed to view links. Register or Login
On another note, Cliff stresses throughout these interviews how very important it was that 305 be kept within V23 (and as close to the center line as possible), precisely because of the chase plane intercepts and trailing that Cliff says began at the Toledo intersection, which he had to personally manage. He says things got hectic when he had to bring the T33 in, in addition to the F-106s covering with their narrow radar cones, crossing on the west side of PDX ...

Cliff is saying he and 305 were in a 'close working relationship'. And keeping 305 as close to the center line of V23 as possible was important - in order to facilitate the F106s intercept with 305 starting at Toledo. If 305 had strayed from V23 starting at Toledo, he (Cliff) would have known that and had to inform the F106's accordingly. Cliff says 305 did not start a 'straight line' path on its own starting at Toledo to Canby but was ordered to stay on V23 and never strayed from that instruction.   

See my post above before Georger added the last paragraph to his amended post.  I stand by my post.

If the airliner had stayed on the centerline of V-23, it would have passed on the east side of Portland.  So Ammerman has made contradictory statements and apparently at the same time.

Himmelsbach's book supports a west side bypass of Portland and he was airborne in a helicopter that evening.  Plus the T-33 took off from Portland and headed west before becoming involved with the hijacking.  There is plenty of other evidence to support a west side bypass and not a single thing, Ammerman's statement otherwise, to support an east side bypass.
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2372 on: July 30, 2019, 03:02:52 PM »
As mentioned on the other page I don't see a bypass on anything. why would it only be Portland? I just posted that they flew over "heavy populated" area's in Reno/Sparks. no cross talk regarding any area's out of the question. they were given the sky to fly..
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2373 on: July 30, 2019, 03:05:44 PM »
You are not allowed to view links. Register or Login
As mentioned on the other page I don't see a bypass on anything. why would it only be Portland? I just posted that they flew over "heavy populated" area's in Reno/Sparks. no cross talk regarding any area's out of the question. they were given the sky to fly..

That is my interpretation too.
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2374 on: July 30, 2019, 03:17:22 PM »
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
On another note, Cliff stresses throughout these interviews how very important it was that 305 be kept within V23 (and as close to the center line as possible), precisely because of the chase plane intercepts and trailing that Cliff says began at the Toledo intersection, which he had to personally manage. He says things got hectic when he had to bring the T33 in, in addition to the F-106s covering with their narrow radar cones, crossing on the west side of PDX ...

Cliff is saying he and 305 were in a 'close working relationship'. And keeping 305 as close to the center line of V23 as possible was important - in order to facilitate the F106s intercept with 305 starting at Toledo. If 305 had strayed from V23 starting at Toledo, he (Cliff) would have known that and had to inform the F106's accordingly. Cliff says 305 did not start a 'straight line' path on its own starting at Toledo to Canby but was ordered to stay on V23 and never strayed from that instruction.   

See my post above before Georger added the last paragraph to his amended post.  I stand by my post.

If the airliner had stayed on the centerline of V-23, it would have passed on the east side of Portland.  So Ammerman has made contradictory statements and apparently at the same time.

Himmelsbach's book supports a west side bypass of Portland and he was airborne in a helicopter that evening.  Plus the T-33 took off from Portland and headed west before becoming involved with the hijacking.  There is plenty of other evidence to support a west side bypass and not a single thing, Ammerman's statement otherwise, to support an east side bypass.

You are knit-picking. Ammerman's statement is 'as close to the center line of V23 as possible'. He then says in his interview ' if 305 strayed at all it would have been to the western side of V23 at PDX, but only when it crossed as I wasnt watching my screen (doing radio work) when 305 crossed ...'

You keep looking for contradictions that you can drive a squadron of tanks through! Ammerman's testimony is completely consistent especially in his description of where 305 was from Toledo clear down to Eugene. He was there. You weren't!

In addition, Ammerman explains WHY it was so important to keep 305 within V23, to facilitate the F106 and T33 intercepts and trailing - starting at Toledo! With the F106's being hindered further by a narrow radar nose return! Cliff's instructions to the chase planes was critical all the way from Toledo clear down to south of PDX.

Did you interview Cliff or not? I thot you did? By email ?
« Last Edit: July 30, 2019, 03:21:19 PM by georger »
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2375 on: July 30, 2019, 03:21:00 PM »
This is getting consistent with the way people with suspects comment. the DNA comes back negative, well it must not be Cooper's. the witness says no and they look for loopholes to fly through. we have multiple reports from multiple radar operators. it's a shame the cloud coverage was there. Portland would of seen the plane from the tower.
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2376 on: July 30, 2019, 03:28:34 PM »
You are not allowed to view links. Register or Login
This is getting consistent with the way people with suspects comment. the DNA comes back negative, well it must not be Cooper's. the witness says no and they look for loopholes to fly through. we have multiple reports from multiple radar operators. it's a shame the cloud coverage was there. Portland would of seen the plane from the tower.

Ive always wondered if there were people out looking! Maybe that's why Janet and her husband were looking?

Today there would be news people with cameras out waiting-looking. 
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2377 on: July 31, 2019, 07:07:29 AM »
The question is whether Ammerman was ARTCC or TRACON. he said he was at SEATAC. the ARTCC has been away from the airport since 1962.

TRACON handles flights coming in and flights taking off then it's handed off to ARTCC.

ARTCCs, usually referred to as "Centers," are established primarily to provide Air Traffic Service to aircraft operating on IFR flight plans within the controlled airspace, and principally during the en route phase of flight.

There are 21 Air Route Traffic Control Centers (ARTCC) in the United States.

Any aircraft operating under Instrument Flight Rules (IFR) within the confines of an ARTCC's airspace is controlled by air traffic controllers at the Center. This includes all sorts of different types of aircraft: privately owned single engine aircraft, commuter airlines, military jets and commercial airlines.

Is the information I've provided inaccurate or is Ammerman going off second hand information? he sounds like he knows what he's talking about.
« Last Edit: July 31, 2019, 07:08:55 AM by Shutter »
 

Offline Robert99

  • Hero Member
  • *****
  • Posts: 1711
  • Thanked: 196 times
Re: Flight Path And Related Issues
« Reply #2378 on: July 31, 2019, 01:33:30 PM »
You are not allowed to view links. Register or Login
The question is whether Ammerman was ARTCC or TRACON. he said he was at SEATAC. the ARTCC has been away from the airport since 1962.

TRACON handles flights coming in and flights taking off then it's handed off to ARTCC.

ARTCCs, usually referred to as "Centers," are established primarily to provide Air Traffic Service to aircraft operating on IFR flight plans within the controlled airspace, and principally during the en route phase of flight.

There are 21 Air Route Traffic Control Centers (ARTCC) in the United States.

Any aircraft operating under Instrument Flight Rules (IFR) within the confines of an ARTCC's airspace is controlled by air traffic controllers at the Center. This includes all sorts of different types of aircraft: privately owned single engine aircraft, commuter airlines, military jets and commercial airlines.

Is the information I've provided inaccurate or is Ammerman going off second hand information? he sounds like he knows what he's talking about.

It is my understanding that the radar system for the Seattle area was physically located at McChord AFB.  It would probably be operated by USAF military and civilian personnel.  The FAA air traffic controllers may not have been directly involved in its operation.

There was probably a Memorandum of Understanding between the USAF and the FAA about the use of the radar data.  In any event, the Seattle air traffic controllers in Auburn would have displays from this radar at their work stations.  The Auburn controllers probably had displays from radar systems in the Spokane area as well as other areas for which they were responsible for air traffic control.

The approach and departure controllers at SEATAC would also have displays from the McChord radar and/or they might also have displays from lower powered radars located at SEATAC itself.  These controllers would probably be located in the SEATAC tower building very close to the tower controllers who were looking out the windows.  All of these people would work very closely together.

The NWA airliner was cleared for take-off on the ground control frequency and told to contact the Seattle ATC center directly on a specific frequency.  They therefore bypassed the tower controller and the departure controller.  Apparently there was some confusion between the SEATAC tower controllers and the ATC controllers in Auburn.  When the airliner contacted the Auburn controllers, they were apparently taken by surprise and had to ask the airliner for information.  This took a couple of minutes to clear up and I think it is discussed in the "FBI Notes" and other places.

In the Portland area, there was probably a low power radar station that provided coverage that was not available from the Seattle ATC radar system.  This station would probably be located on the PIA property (maybe on top of the tower cab).  Presumably it was just such a station that claimed to have tracked the airliner in the Portland area.  This station would be entirely separate from the enroute radar network at Auburn.  The mountains between Seattle and Portland would block the two radars.

Previous posts on this site have stated that the F-106s broke off their trailing of the airliner, climbed to 20,000 feet, and headed east while still north of the Columbia River.  Ammerman claims to have been the controller who worked the intercept problem between the T-33 (and also presumably the F-106s) and the airliner.  He would almost certainly have been at the Seattle ATC in Auburn.  Also, he would probably have been assisted by several other people.  And I imagine that the most senior managers at the Auburn facility were looking over his should (and that of the other controllers involved) as he worked the interception.  This hijacking was not a routine event so it would be an "all hands on deck" situation.

Ammerman has apparently told Georger that he was not looking at his radar display from some point where the airliner was north of the Columbia River until it was south of the Columbia River.  But you can rest assured that someone was looking at that display.  And it appears that the other people were giving the airliner instructions that Ammerman was not aware of while he was working on the interception matter.

During the hand off to the Oakland Center, at least four Oakland controllers were involved.  Only one Seattle Center controller was involved apparently. 
« Last Edit: July 31, 2019, 01:37:14 PM by Robert99 »
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2379 on: July 31, 2019, 03:06:58 PM »
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
The question is whether Ammerman was ARTCC or TRACON. he said he was at SEATAC. the ARTCC has been away from the airport since 1962.

TRACON handles flights coming in and flights taking off then it's handed off to ARTCC.

ARTCCs, usually referred to as "Centers," are established primarily to provide Air Traffic Service to aircraft operating on IFR flight plans within the controlled airspace, and principally during the en route phase of flight.

There are 21 Air Route Traffic Control Centers (ARTCC) in the United States.

Any aircraft operating under Instrument Flight Rules (IFR) within the confines of an ARTCC's airspace is controlled by air traffic controllers at the Center. This includes all sorts of different types of aircraft: privately owned single engine aircraft, commuter airlines, military jets and commercial airlines.

Is the information I've provided inaccurate or is Ammerman going off second hand information? he sounds like he knows what he's talking about.

It is my understanding that the radar system for the Seattle area was physically located at McChord AFB.  It would probably be operated by USAF military and civilian personnel.  The FAA air traffic controllers may not have been directly involved in its operation.

There was probably a Memorandum of Understanding between the USAF and the FAA about the use of the radar data.  In any event, the Seattle air traffic controllers in Auburn would have displays from this radar at their work stations.  The Auburn controllers probably had displays from radar systems in the Spokane area as well as other areas for which they were responsible for air traffic control.

The approach and departure controllers at SEATAC would also have displays from the McChord radar and/or they might also have displays from lower powered radars located at SEATAC itself.  These controllers would probably be located in the SEATAC tower building very close to the tower controllers who were looking out the windows.  All of these people would work very closely together.

The NWA airliner was cleared for take-off on the ground control frequency and told to contact the Seattle ATC center directly on a specific frequency.  They therefore bypassed the tower controller and the departure controller.  Apparently there was some confusion between the SEATAC tower controllers and the ATC controllers in Auburn.  When the airliner contacted the Auburn controllers, they were apparently taken by surprise and had to ask the airliner for information.  This took a couple of minutes to clear up and I think it is discussed in the "FBI Notes" and other places.

In the Portland area, there was probably a low power radar station that provided coverage that was not available from the Seattle ATC radar system.  This station would probably be located on the PIA property (maybe on top of the tower cab).  Presumably it was just such a station that claimed to have tracked the airliner in the Portland area.  This station would be entirely separate from the enroute radar network at Auburn.  The mountains between Seattle and Portland would block the two radars.

Previous posts on this site have stated that the F-106s broke off their trailing of the airliner, climbed to 20,000 feet, and headed east while still north of the Columbia River.  Ammerman claims to have been the controller who worked the intercept problem between the T-33 (and also presumably the F-106s) and the airliner.  He would almost certainly have been at the Seattle ATC in Auburn.  Also, he would probably have been assisted by several other people.  And I imagine that the most senior managers at the Auburn facility were looking over his should (and that of the other controllers involved) as he worked the interception.  This hijacking was not a routine event so it would be an "all hands on deck" situation.

Ammerman has apparently told Georger that he was not looking at his radar display from some point where the airliner was north of the Columbia River until it was south of the Columbia River.  But you can rest assured that someone was looking at that display.  And it appears that the other people were giving the airliner instructions that Ammerman was not aware of while he was working on the interception matter.

During the hand off to the Oakland Center, at least four Oakland controllers were involved.  Only one Seattle Center controller was involved apparently.

I have a feeling this is going to get *very* complicated, due to hair splitting, the system Cliff was part of, etc - looking for anything that will nullify Ammerman's testimony ?

From my notes:

"Cliff was a controller located at Seattle Center who handled 305 all the way to PDX and slightly beyond PDX  on the evening of 11-24-71.  Cliff handed off to Eugene. Departure control gave over 305 to Cliff and Cliff handled 305. Cliff was not SEAR2 in the NWA transcript.  Cliff says whoever R2 was, R2 would have handed off to R4, who would have handed off to R5 etc.  Cliff was located at Seattle Center. Seattle Center was one of 22-26 large air control centers at the time in the US.  Seattle Center was in a building below the tower at SEA-TAC."

And: 'Cliff suggests we contact the FAA Northwest Region who he feels kept and still has ‘all the radar input and any controller transcripts and notes'  “if those were kept at all from that night”, he says.

This complexity is the whole reason I wanted R99 to talk to Cliff. Apparently that never happened!
« Last Edit: July 31, 2019, 03:11:46 PM by georger »
 
The following users thanked this post: andrade1812

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2380 on: July 31, 2019, 04:39:53 PM »
Quote
Cliff was located at Seattle Center. Seattle Center was one of 22-26 large air control centers at the time in the US.  Seattle Center was in a building below the tower at SEA-TAC."

I truly understand all of this, but, it does conflict with the FAA website stating the ARTCC has been at it's present location since 1962. that is the "Seattle Center"...this isn't splitting hairs when we have an obvious conflict. It clearly states it was at SeaTac in the 50's and moved from SeaTac in 1962.

1963 - Spokane ARTCC was transferred to the Seattle ARTCC

It's on the page after the Table Of Contents

You are not allowed to view links. Register or Login
« Last Edit: July 31, 2019, 05:01:13 PM by Shutter »
 

Offline Robert99

  • Hero Member
  • *****
  • Posts: 1711
  • Thanked: 196 times
Re: Flight Path And Related Issues
« Reply #2381 on: July 31, 2019, 04:56:04 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
The question is whether Ammerman was ARTCC or TRACON. he said he was at SEATAC. the ARTCC has been away from the airport since 1962.

TRACON handles flights coming in and flights taking off then it's handed off to ARTCC.

ARTCCs, usually referred to as "Centers," are established primarily to provide Air Traffic Service to aircraft operating on IFR flight plans within the controlled airspace, and principally during the en route phase of flight.

There are 21 Air Route Traffic Control Centers (ARTCC) in the United States.

Any aircraft operating under Instrument Flight Rules (IFR) within the confines of an ARTCC's airspace is controlled by air traffic controllers at the Center. This includes all sorts of different types of aircraft: privately owned single engine aircraft, commuter airlines, military jets and commercial airlines.

Is the information I've provided inaccurate or is Ammerman going off second hand information? he sounds like he knows what he's talking about.

It is my understanding that the radar system for the Seattle area was physically located at McChord AFB.  It would probably be operated by USAF military and civilian personnel.  The FAA air traffic controllers may not have been directly involved in its operation.

There was probably a Memorandum of Understanding between the USAF and the FAA about the use of the radar data.  In any event, the Seattle air traffic controllers in Auburn would have displays from this radar at their work stations.  The Auburn controllers probably had displays from radar systems in the Spokane area as well as other areas for which they were responsible for air traffic control.

The approach and departure controllers at SEATAC would also have displays from the McChord radar and/or they might also have displays from lower powered radars located at SEATAC itself.  These controllers would probably be located in the SEATAC tower building very close to the tower controllers who were looking out the windows.  All of these people would work very closely together.

The NWA airliner was cleared for take-off on the ground control frequency and told to contact the Seattle ATC center directly on a specific frequency.  They therefore bypassed the tower controller and the departure controller.  Apparently there was some confusion between the SEATAC tower controllers and the ATC controllers in Auburn.  When the airliner contacted the Auburn controllers, they were apparently taken by surprise and had to ask the airliner for information.  This took a couple of minutes to clear up and I think it is discussed in the "FBI Notes" and other places.

In the Portland area, there was probably a low power radar station that provided coverage that was not available from the Seattle ATC radar system.  This station would probably be located on the PIA property (maybe on top of the tower cab).  Presumably it was just such a station that claimed to have tracked the airliner in the Portland area.  This station would be entirely separate from the enroute radar network at Auburn.  The mountains between Seattle and Portland would block the two radars.

Previous posts on this site have stated that the F-106s broke off their trailing of the airliner, climbed to 20,000 feet, and headed east while still north of the Columbia River.  Ammerman claims to have been the controller who worked the intercept problem between the T-33 (and also presumably the F-106s) and the airliner.  He would almost certainly have been at the Seattle ATC in Auburn.  Also, he would probably have been assisted by several other people.  And I imagine that the most senior managers at the Auburn facility were looking over his should (and that of the other controllers involved) as he worked the interception.  This hijacking was not a routine event so it would be an "all hands on deck" situation.

Ammerman has apparently told Georger that he was not looking at his radar display from some point where the airliner was north of the Columbia River until it was south of the Columbia River.  But you can rest assured that someone was looking at that display.  And it appears that the other people were giving the airliner instructions that Ammerman was not aware of while he was working on the interception matter.

During the hand off to the Oakland Center, at least four Oakland controllers were involved.  Only one Seattle Center controller was involved apparently.

I have a feeling this is going to get *very* complicated, due to hair splitting, the system Cliff was part of, etc - looking for anything that will nullify Ammerman's testimony ?

From my notes:

"Cliff was a controller located at Seattle Center who handled 305 all the way to PDX and slightly beyond PDX  on the evening of 11-24-71.  Cliff handed off to Eugene. Departure control gave over 305 to Cliff and Cliff handled 305. Cliff was not SEAR2 in the NWA transcript.  Cliff says whoever R2 was, R2 would have handed off to R4, who would have handed off to R5 etc.  Cliff was located at Seattle Center. Seattle Center was one of 22-26 large air control centers at the time in the US.  Seattle Center was in a building below the tower at SEA-TAC."

And: 'Cliff suggests we contact the FAA Northwest Region who he feels kept and still has ‘all the radar input and any controller transcripts and notes'  “if those were kept at all from that night”, he says.

This complexity is the whole reason I wanted R99 to talk to Cliff. Apparently that never happened!

Georger, please read this post before replying.  There is no hair splitting here.

Here are the Seattle controllers listed on the front page of the Seattle ATC radio transcripts (note that an R4 is not listed):

  R2
  R5
  R6
  R10

The Seattle ATC radio transcripts are described as being a "true transcription" by Gerald H. Osterkamp, Chief, Seattle ARTCC.  He adds that the original transcripts are on file in his office.

Did you read Shutter's post about when the Seattle ATC was opened in Auburn?  If not, you might find it interesting compared to what you have written above.

The FAA does keep records of aircraft accidents and incidents such as this hijacking.  For the Seattle area, this records are eventually retired to the FAA Regional Office in the Seattle area.  If you remember, that FAA Regional Office is the one that I initially contacted several years ago in an effort to obtain the unredacted Seattle ATC radio transcripts.

That FAA Regional Office promptly replied to my inquiry with a full page of contact information for the FBI FOIA office in Winchester, Virginia.  And they replied by registered mail.

I contacted that FBI FOIA office and got a run-around, then I appealed to the DOJ and got another run-around.  After that I contacted my US Congresswoman, who is now a US Senator filling out the remainder of John McCain's term.  Three Congressional interventions later, I received exactly two pages of information but nothing on the radio transcripts.  Those two pages are posted here on Shutter's site.

All of the above has been discussed here and at DZ at great length over the last several years.

If you are interested in contacting Ammerman again, let me know and I can suggest some specific questions you might want to discuss with him.  This assumes that you have a working relationship with him.     

« Last Edit: July 31, 2019, 05:00:25 PM by Robert99 »
 

Offline Shutter

  • Administrator
  • Hero Member
  • *****
  • Posts: 9300
  • Thanked: 1024 times
Re: Flight Path And Related Issues
« Reply #2382 on: July 31, 2019, 04:57:58 PM »
FAA Air Route Traffic Control Centers (1960-Present) - A Federal Aviation Administration (FAA) system of 25 Air Route Traffic Control Centers (ARTCC)s operated with radar data provided by FAA radar sites, DoD radar sites, and other federal agency radar sites. These centers provide en route and oceanic services to private, commercial and military aircraft overflying their respective control areas. As aircraft enter or exit from one control area to the next, responsibility for the aircraft is transferred to the gaining ARTCC. Voice communication between aircraft and the ARTCCs is supported by a network of ground-air radio sites.

In addition to the 25 FAA ARTCCs, there are 160 FAA Terminal Radar Approach Control (TRACON) facilities that provide services at terminals (airfields) these facilities have separate supporting radar and radio systems. The nations military airfields generally provide their own terminal services or share with FAA facilities when the airfields are joint use with civil aviation.

The gathering of radar and other sensor data is now largely automated and continuous but the actions necessary to control the airspace are conversational and require some 14,000 FAA air traffic controllers talking directly to pilots in the air and on the ground at terminals. This number does not include military air traffic controllers.
« Last Edit: July 31, 2019, 05:07:32 PM by Shutter »
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2383 on: July 31, 2019, 05:55:53 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
The question is whether Ammerman was ARTCC or TRACON. he said he was at SEATAC. the ARTCC has been away from the airport since 1962.

TRACON handles flights coming in and flights taking off then it's handed off to ARTCC.

ARTCCs, usually referred to as "Centers," are established primarily to provide Air Traffic Service to aircraft operating on IFR flight plans within the controlled airspace, and principally during the en route phase of flight.

There are 21 Air Route Traffic Control Centers (ARTCC) in the United States.

Any aircraft operating under Instrument Flight Rules (IFR) within the confines of an ARTCC's airspace is controlled by air traffic controllers at the Center. This includes all sorts of different types of aircraft: privately owned single engine aircraft, commuter airlines, military jets and commercial airlines.

Is the information I've provided inaccurate or is Ammerman going off second hand information? he sounds like he knows what he's talking about.

It is my understanding that the radar system for the Seattle area was physically located at McChord AFB.  It would probably be operated by USAF military and civilian personnel.  The FAA air traffic controllers may not have been directly involved in its operation.

There was probably a Memorandum of Understanding between the USAF and the FAA about the use of the radar data.  In any event, the Seattle air traffic controllers in Auburn would have displays from this radar at their work stations.  The Auburn controllers probably had displays from radar systems in the Spokane area as well as other areas for which they were responsible for air traffic control.

The approach and departure controllers at SEATAC would also have displays from the McChord radar and/or they might also have displays from lower powered radars located at SEATAC itself.  These controllers would probably be located in the SEATAC tower building very close to the tower controllers who were looking out the windows.  All of these people would work very closely together.

The NWA airliner was cleared for take-off on the ground control frequency and told to contact the Seattle ATC center directly on a specific frequency.  They therefore bypassed the tower controller and the departure controller.  Apparently there was some confusion between the SEATAC tower controllers and the ATC controllers in Auburn.  When the airliner contacted the Auburn controllers, they were apparently taken by surprise and had to ask the airliner for information.  This took a couple of minutes to clear up and I think it is discussed in the "FBI Notes" and other places.

In the Portland area, there was probably a low power radar station that provided coverage that was not available from the Seattle ATC radar system.  This station would probably be located on the PIA property (maybe on top of the tower cab).  Presumably it was just such a station that claimed to have tracked the airliner in the Portland area.  This station would be entirely separate from the enroute radar network at Auburn.  The mountains between Seattle and Portland would block the two radars.

Previous posts on this site have stated that the F-106s broke off their trailing of the airliner, climbed to 20,000 feet, and headed east while still north of the Columbia River.  Ammerman claims to have been the controller who worked the intercept problem between the T-33 (and also presumably the F-106s) and the airliner.  He would almost certainly have been at the Seattle ATC in Auburn.  Also, he would probably have been assisted by several other people.  And I imagine that the most senior managers at the Auburn facility were looking over his should (and that of the other controllers involved) as he worked the interception.  This hijacking was not a routine event so it would be an "all hands on deck" situation.

Ammerman has apparently told Georger that he was not looking at his radar display from some point where the airliner was north of the Columbia River until it was south of the Columbia River.  But you can rest assured that someone was looking at that display.  And it appears that the other people were giving the airliner instructions that Ammerman was not aware of while he was working on the interception matter.

During the hand off to the Oakland Center, at least four Oakland controllers were involved.  Only one Seattle Center controller was involved apparently.

I have a feeling this is going to get *very* complicated, due to hair splitting, the system Cliff was part of, etc - looking for anything that will nullify Ammerman's testimony ?

From my notes:

"Cliff was a controller located at Seattle Center who handled 305 all the way to PDX and slightly beyond PDX  on the evening of 11-24-71.  Cliff handed off to Eugene. Departure control gave over 305 to Cliff and Cliff handled 305. Cliff was not SEAR2 in the NWA transcript.  Cliff says whoever R2 was, R2 would have handed off to R4, who would have handed off to R5 etc.  Cliff was located at Seattle Center. Seattle Center was one of 22-26 large air control centers at the time in the US.  Seattle Center was in a building below the tower at SEA-TAC."

And: 'Cliff suggests we contact the FAA Northwest Region who he feels kept and still has ‘all the radar input and any controller transcripts and notes'  “if those were kept at all from that night”, he says.

This complexity is the whole reason I wanted R99 to talk to Cliff. Apparently that never happened!

Georger, please read this post before replying.  There is no hair splitting here.

Here are the Seattle controllers listed on the front page of the Seattle ATC radio transcripts (note that an R4 is not listed):

  R2
  R5
  R6
  R10

The Seattle ATC radio transcripts are described as being a "true transcription" by Gerald H. Osterkamp, Chief, Seattle ARTCC.  He adds that the original transcripts are on file in his office.

Did you read Shutter's post about when the Seattle ATC was opened in Auburn?  If not, you might find it interesting compared to what you have written above.

The FAA does keep records of aircraft accidents and incidents such as this hijacking.  For the Seattle area, this records are eventually retired to the FAA Regional Office in the Seattle area.  If you remember, that FAA Regional Office is the one that I initially contacted several years ago in an effort to obtain the unredacted Seattle ATC radio transcripts.

That FAA Regional Office promptly replied to my inquiry with a full page of contact information for the FBI FOIA office in Winchester, Virginia.  And they replied by registered mail.

I contacted that FBI FOIA office and got a run-around, then I appealed to the DOJ and got another run-around.  After that I contacted my US Congresswoman, who is now a US Senator filling out the remainder of John McCain's term.  Three Congressional interventions later, I received exactly two pages of information but nothing on the radio transcripts.  Those two pages are posted here on Shutter's site.

All of the above has been discussed here and at DZ at great length over the last several years.

If you are interested in contacting Ammerman again, let me know and I can suggest some specific questions you might want to discuss with him.  This assumes that you have a working relationship with him.   

This assumes that you have a working relationship with him.   ?

Nothing new in your reply including the smarm.

So let me say it again and maybe this time you can HEAR IT!  Why didn't you go ahead and interview Ammerman like I thought you were going to do? I always told you I preferred you interview him - not me! My interviews of CA were preliminary to you interviewing him - as I recall I even asked you 'what questions shall I ask?' I think I asked you again between my interviews, based on the first interview conducted.

For all I know you could be correct. The one thing I do know is: I am though with your childish shit. Good luck.  :rofl:

And you can take that to the bank! I am not going to e in the middle of this shit any more.  :congrats:
« Last Edit: July 31, 2019, 06:02:57 PM by georger »
 

Offline georger

  • Hero Member
  • *****
  • Posts: 3182
  • Thanked: 467 times
Re: Flight Path And Related Issues
« Reply #2384 on: July 31, 2019, 06:00:09 PM »
You are not allowed to view links. Register or Login
FAA Air Route Traffic Control Centers (1960-Present) - A Federal Aviation Administration (FAA) system of 25 Air Route Traffic Control Centers (ARTCC)s operated with radar data provided by FAA radar sites, DoD radar sites, and other federal agency radar sites. These centers provide en route and oceanic services to private, commercial and military aircraft overflying their respective control areas. As aircraft enter or exit from one control area to the next, responsibility for the aircraft is transferred to the gaining ARTCC. Voice communication between aircraft and the ARTCCs is supported by a network of ground-air radio sites.

In addition to the 25 FAA ARTCCs, there are 160 FAA Terminal Radar Approach Control (TRACON) facilities that provide services at terminals (airfields) these facilities have separate supporting radar and radio systems. The nations military airfields generally provide their own terminal services or share with FAA facilities when the airfields are joint use with civil aviation.

The gathering of radar and other sensor data is now largely automated and continuous but the actions necessary to control the airspace are conversational and require some 14,000 FAA air traffic controllers talking directly to pilots in the air and on the ground at terminals. This number does not include military air traffic controllers.

Whatever alternate factoids you have, I can only respond with what CA told me. That's the best I can do.

Find him and call hm and ask him yourself! 

Or, find him and dont call him and rely on your own alternate factoids instead and put this to bed. Maybe Flyjack knows? Maybe Blevins knows at Dropzone? 
« Last Edit: July 31, 2019, 06:05:16 PM by georger »