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

georger

  • Guest
Re: Flight Path And Related Issues
« Reply #135 on: March 25, 2014, 04:59:56 PM »
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
As you know, I completely reject the idea of the airliner passing on the east side of Portland.  It just doesn't make any sense for the aircraft to deviate so far from the route to Reno.

Also, the flight crew would NOT, repeat NOT, wait until they were past the Portland VORTAC to determine what they would do next.  There were three pilots in the cockpit that evening.  Anderson may have been acting as the Flight Engineer on that flight, but he was also a pilot.  They probably would have been planning their route at least 30 minutes ahead.  And simplicity itself would be to just fly a straight line from the area of the Mayfield/Malay Intersection to a point south of Portland where they would rejoin V-23.  Pilots who are interested in staying alive plan ahead.

The only "clearance" given to the airliner that evening by ATC was to "do whatever you have to and we will keep people out of your way".  Basically, the airliner had the right of way over all other aircraft that evening with the exception of aircraft experiencing real emergencies (such as fires, running out of fuel, etc.).

Yes, as I expected.  As usual, you give no consideration to the idea that they were placing great importance on getting the guy out of the plane.   That's what he said he wanted.  He was in charge.  What we have available says they were preoccupied/focused on helping him get out.  Had they been able to get him out and be sure of it, they might even have been able to land at PDX.  They didn't want to go to Reno.  Whatever they did near Portland may even have been so because of the possibility of landing there.

I happened to agree with this. Getting Cooper GONE was their top priority ~8:45 - 8:20. This is evidenced in crew interviews and the Transcripts we have...

After 8:20 things seem to have eased up, except they still weren't 100% sure he was gone, until finally near Reno Scott says: 'Im going back and look', and he comes back and reports: 'Apparently our friend has taken leave of us'.

And, he went back and looked in spite of being told not to!
 

« Last Edit: March 25, 2014, 05:03:53 PM by georger »
 

georger

  • Guest
Re: Flight Path And Related Issues
« Reply #136 on: March 25, 2014, 05:02:20 PM »
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
We know that whatever route they flew they had a rendezvous with a T33 (being vectored with 305 by R2) in some rather narrow time period south of Portland near Lake Oswego - an undeniable fact.

What airport was the T33 out of?  Any info about what it was doing and where it was leading up to the rendezvous?

R99 should have that. I would have to look it up, but the rendezvous was very near Lake Oswego, if not over it, south of Portland in the ___?___ time slot.

BTW!  Talking to and instructing the T33 is the whole reason R2 said: "That is reason I wasn't watching 305 when it crossed the Columbia to know exactly where it was (east, over, or west of Portland) but my impression is it was right on the center-line of V23 when it crossed the Columbia at Portland". I think, am fairly sure, R99 got the same story from R2 when he talked to him...  

« Last Edit: March 25, 2014, 05:10:31 PM by georger »
 

Offline hom

  • Full Member
  • ***
  • Posts: 113
Re: Flight Path And Related Issues
« Reply #137 on: March 25, 2014, 05:08:39 PM »
You are not allowed to view links. Register or Login
R99 should have that. I would have to look it up, but the rendezvous was very near to Lake Oswego south of Portland in the ___?___ time slot.

It seems likely that 305 might have sped up a bit from Scholl to V23 in order to get in front of the T33, and maybe slowed down a bit near Oswego to facilitate a rendezvous.  The "FBI" plot indicates both of these.

Really gotta go!
« Last Edit: March 25, 2014, 05:11:42 PM by hom »
 

georger

  • Guest
Re: Flight Path And Related Issues
« Reply #138 on: March 25, 2014, 05:11:29 PM »
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
R99 should have that. I would have to look it up, but the rendezvous was very near to Lake Oswego south of Portland in the ___?___ time slot.

It seems likely that 305 might have sped up a bit from Scholl to V23 in order to get in front of the T33, and maybe slowed down a bit near Oswego to facilitate a rendezvous.  The "FBI" plot indicates both of these.

Just edited mine above to include:

BTW!  Talking to and instructing the T33 is the whole reason R2 said: "That is reason I wasn't watching 305 on my screen when it crossed the Columbia to know exactly where it was (east, over, or west of Portland) but my impression is it was right on the center-line of V23 when it crossed the Columbia at Portland". I think, am fairly sure, R99 got the same story from R2 when he talked to him... 

I need to run here ... meeting.
« Last Edit: March 25, 2014, 05:13:46 PM by georger »
 

Offline hom

  • Full Member
  • ***
  • Posts: 113
Re: Flight Path And Related Issues
« Reply #139 on: March 25, 2014, 05:43:29 PM »
You are not allowed to view links. Register or Login
Talking to and instructing the T33 is the whole reason R2 said: "That is reason I wasn't watching 305 on my screen when it crossed the Columbia to know exactly where it was (east, over, or west of Portland) but my impression is it was right on the center-line of V23 when it crossed the Columbia at Portland". I think, am fairly sure, R99 got the same story from R2 when he talked to him...

305 speeding up between Scholl and the I-5 bridge area could also have contributed to R2 missing that part.  And account for 305 overshooting and having to turn back to V23, slowing down in the process.  Nothing to do with the control zone.
 

Robert99

  • Guest
Re: Flight Path And Related Issues
« Reply #140 on: March 25, 2014, 05:56:55 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
We know that whatever route they flew they had a rendezvous with a T33 (being vectored with 305 by R2) in some rather narrow time period south of Portland near Lake Oswego - an undeniable fact.

What airport was the T33 out of?  Any info about what it was doing and where it was leading up to the rendezvous?

R99 should have that. I would have to look it up, but the rendezvous was very near Lake Oswego, if not over it, south of Portland in the ___?___ time slot.

BTW!  Talking to and instructing the T33 is the whole reason R2 said: "That is reason I wasn't watching 305 when it crossed the Columbia to know exactly where it was (east, over, or west of Portland) but my impression is it was right on the center-line of V23 when it crossed the Columbia at Portland". I think, am fairly sure, R99 got the same story from R2 when he talked to him...

First, let me point out that I agree that the crew was extremely interested in getting Cooper to jump.  And they were also extremely interested in keeping him calmed down.  So they were doing precisely as he told them to do.  None of this would result in the aircraft making a detour to the east side of Portland.

Himmelsbach states that the T-33 took off to the west and this is supported by the fact that the relatively light ground wind was generally from the southwest.  This means the T-33 would have used runway 28 for the takeoff.  And the T-33 was probably heading to a military practice area which, in view of the terrain, would probably be somewhere west of Portland and maybe over the Pacific.

Refer to Hominid's map in his recent post. Take a look at the four red "x" marks on the west and southwest side of Portland.  There may be more than four of these marks but it is difficult to identify them because of the magenta colors that are on that map.  Someone was plotting points of interest over a distance of more than 10 miles.  Note that there are two sets of two marks each that form a straight line with the Mayfield/Malay Intersection.  Also note that Tina Bar is only about 1000 feet horizontally from these straight lines.  Assuming that the airliner is represented by one of these straight lines, it would rejoin the centerline of V-23 at or very near to the Canby Intersection.

Further, there is a teletypewriter printout in the "FBI notes" that indicates the airliner reported it was "23 DME miles south of Portland", or something like that, and the teletypewriter printout was time stamped (which is the time someone pressed the send button) at 8:22 PM.  While the airliner probably didn't have its tail pointed directly to the Portland VORTAC, it was still traveling away from there at the rate of about 3 DME miles per minute.  This means that the DME counter would only display "23" for about a 20 to 25 second period.

Other information in the "George Harrison Papers" gives various times for that message.  Those times range from 8:18 to 8:22.  The 8:22 time was the time the message was sent by ARINC and it is not known if that was the initial time the message was sent or if this was a redirection of the message to NWA at Portland from somewhere else.

Based on recent discussions with highly knowledgeable people in the communications business, it would probably take some minutes for the people who received the airliner's message on the ground (ARINC) to formulate the message, type it, and then send it.  By contrast, the 8:18 time could be the time someone heard the pilot's radio message on the phone patch from ARINC.  Based on Shutter's simulations and my own analyses, the 8:18 time fits the situation much, much better.
 

Robert99

  • Guest
Re: Flight Path And Related Issues
« Reply #141 on: March 25, 2014, 05:59:21 PM »
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
R99 should have that. I would have to look it up, but the rendezvous was very near to Lake Oswego south of Portland in the ___?___ time slot.

It seems likely that 305 might have sped up a bit from Scholl to V23 in order to get in front of the T33, and maybe slowed down a bit near Oswego to facilitate a rendezvous.  The "FBI" plot indicates both of these.

Really gotta go!

Keep in mind that if the airliner had speeded up, Cooper could have noticed.  And he specifically told them to maintain a constant speed.
 

georger

  • Guest
Re: Flight Path And Related Issues
« Reply #142 on: March 25, 2014, 06:27:57 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
We know that whatever route they flew they had a rendezvous with a T33 (being vectored with 305 by R2) in some rather narrow time period south of Portland near Lake Oswego - an undeniable fact.

What airport was the T33 out of?  Any info about what it was doing and where it was leading up to the rendezvous?

R99 should have that. I would have to look it up, but the rendezvous was very near Lake Oswego, if not over it, south of Portland in the ___?___ time slot.

BTW!  Talking to and instructing the T33 is the whole reason R2 said: "That is reason I wasn't watching 305 when it crossed the Columbia to know exactly where it was (east, over, or west of Portland) but my impression is it was right on the center-line of V23 when it crossed the Columbia at Portland". I think, am fairly sure, R99 got the same story from R2 when he talked to him...

First, let me point out that I agree that the crew was extremely interested in getting Cooper to jump.  And they were also extremely interested in keeping him calmed down.  So they were doing precisely as he told them to do.  None of this would result in the aircraft making a detour to the east side of Portland.

Himmelsbach states that the T-33 took off to the west and this is supported by the fact that the relatively light ground wind was generally from the southwest.  This means the T-33 would have used runway 28 for the takeoff.  And the T-33 was probably heading to a military practice area which, in view of the terrain, would probably be somewhere west of Portland and maybe over the Pacific.

Refer to Hominid's map in his recent post. Take a look at the four red "x" marks on the west and southwest side of Portland.  There may be more than four of these marks but it is difficult to identify them because of the magenta colors that are on that map.  Someone was plotting points of interest over a distance of more than 10 miles.  Note that there are two sets of two marks each that form a straight line with the Mayfield/Malay Intersection.  Also note that Tina Bar is only about 1000 feet horizontally from these straight lines.  Assuming that the airliner is represented by one of these straight lines, it would rejoin the centerline of V-23 at or very near to the Canby Intersection.

Further, there is a teletypewriter printout in the "FBI notes" that indicates the airliner reported it was "23 DME miles south of Portland", or something like that, and the teletypewriter printout was time stamped (which is the time someone pressed the send button) at 8:22 PM.  While the airliner probably didn't have its tail pointed directly to the Portland VORTAC, it was still traveling away from there at the rate of about 3 DME miles per minute.  This means that the DME counter would only display "23" for about a 20 to 25 second period.

Other information in the "George Harrison Papers" gives various times for that message.  Those times range from 8:18 to 8:22.  The 8:22 time was the time the message was sent by ARINC and it is not known if that was the initial time the message was sent or if this was a redirection of the message to NWA at Portland from somewhere else.

Based on recent discussions with highly knowledgeable people in the communications business, it would probably take some minutes for the people who received the airliner's message on the ground (ARINC) to formulate the message, type it, and then send it.  By contrast, the 8:18 time could be the time someone heard the pilot's radio message on the phone patch from ARINC.  Based on Shutter's simulations and my own analyses, the 8:18 time fits the situation much, much better.

All of this is plausible to me, but I have no 'gut instincts' as an experienced commercial pilot from that period or any other. Whatever instincts I have tell me the time slot for the T33 rendezvous is not compatible with an east route,
just not enough time to be in two places at once within reach of each other time-wise. If it would turn out the East route is true that would trash much of the existing data (interview statements etc) that exist. I have pointed that out to JT/Himms a million times and they simply will not budge from their position.

That leaves the FBI or the Dawson flight path, or a merger (somehow) of the two, which preserves an encounter with the T33 near Oswego in the time period assigned that event.

The T33 rendezvous may turn out to be one crucial fact.   


 
       
« Last Edit: March 25, 2014, 06:29:39 PM by georger »
 

georger

  • Guest
Re: Flight Path And Related Issues
« Reply #143 on: March 25, 2014, 11:40:31 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
R99 should have that. I would have to look it up, but the rendezvous was very near to Lake Oswego south of Portland in the ___?___ time slot.

It seems likely that 305 might have sped up a bit from Scholl to V23 in order to get in front of the T33, and maybe slowed down a bit near Oswego to facilitate a rendezvous.  The "FBI" plot indicates both of these.

Really gotta go!

Keep in mind that if the airliner had speeded up, Cooper could have noticed.  And he specifically told them to maintain a constant speed.

Robt99, what time do you have for the T33 intercept?  8:22 time frame?
 
 

Robert99

  • Guest
Re: Flight Path And Related Issues
« Reply #144 on: March 26, 2014, 12:30:57 AM »
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
R99 should have that. I would have to look it up, but the rendezvous was very near to Lake Oswego south of Portland in the ___?___ time slot.

It seems likely that 305 might have sped up a bit from Scholl to V23 in order to get in front of the T33, and maybe slowed down a bit near Oswego to facilitate a rendezvous.  The "FBI" plot indicates both of these.

Really gotta go!

Keep in mind that if the airliner had speeded up, Cooper could have noticed.  And he specifically told them to maintain a constant speed.

Robt99, what time do you have for the T33 intercept?  8:22 time frame?

Looking at Hominid's map again, and assuming that the eastern two large red "x"s are points on the airliner's path, and that it flew directly from the Mayfield/Malay Intersection to the Canby Intersection, then the western two large red "x"s are probably points on the T-33's flight path.

In addition to the two eastern red "x"s, there appears to be a third red "x" on that same line and just west of the words "Williamette" and "Caution".  I think I can see both a vertical line and a horizontal line with both of them being partially obscured by the large black line that is supposed to be the airliner's flight path.  Also, I think I can see a sixth red "x" which would be the third red "x" on the western lines and it is located just slightly below the east end of the word "Wilsonville".

If the "x" marks above are as assumed, or even if the airliner is the western set of marks and the T-33 the eastern set of marks, then both aircraft were headed directly for the Canby Intersection which is the intersection of that 085 radial and V-23.

Further, assuming that the above assumptions are correct and that the time at the "23 DME" location was 8:18, the airliner would have been about 1 or 2 nautical miles west of the V-23 center line at that point and about 4 nautical miles north of the Canby Intersection.  So the airliner would arrive at the Canby Intersection no later than about 8:20.

It is not really possible to estimate the time the T-33 intercepted the airliner but their "flight paths" are reasonably close for all marked points.  It should also be noted that the T-33 probably had a 50 to 100 MPH speed advantage over the airliner.  So maybe the controller put the T-33 on a parallel track to the airliner and used his radar to estimate how far T-33 was behind the airliner.
 

Offline hom

  • Full Member
  • ***
  • Posts: 113
Re: Flight Path And Related Issues
« Reply #145 on: March 26, 2014, 01:22:26 AM »
You are not allowed to view links. Register or Login
First, let me point out that I agree that the crew was extremely interested in getting Cooper to jump.  And they were also extremely interested in keeping him calmed down.  So they were doing precisely as he told them to do.  None of this would result in the aircraft making a detour to the east side of Portland.

I'm not supporting any detour to the east of Portland.  The impacts of any demands he may have been making are uncertain.

Quote
Himmelsbach states that the T-33 took off to the west and this is supported by the fact that the relatively light ground wind was generally from the southwest.  This means the T-33 would have used runway 28 for the takeoff.  And the T-33 was probably heading to a military practice area which, in view of the terrain, would probably be somewhere west of Portland and maybe over the Pacific.

Why do you mention where it was probably heading?  Was it already headed there and got called back to trail 305?

Quote
Refer to Hominid's map in his recent post. Take a look at the four red "x" marks on the west and southwest side of Portland.  There may be more than four of these marks but it is difficult to identify them because of the magenta colors that are on that map.  Someone was plotting points of interest over a distance of more than 10 miles.  Note that there are two sets of two marks each that form a straight line with the Mayfield/Malay Intersection.  Also note that Tina Bar is only about 1000 feet horizontally from these straight lines.  Assuming that the airliner is represented by one of these straight lines, it would rejoin the centerline of V-23 at or very near to the Canby Intersection.

Those 4 "+" marks were mistakes.  They're crossed out.  Don't you use image editing software so you can magnify the images?  There are only the four.  They are each plotted exactly 5 minutes of longitude to the west of the correct positions.  This was no doubt a result of the fact that the minute marks are not labelled.   Just click or double click on the "ploterrors.bmp" and something on your computer should open it so you can magnify it.

Quote
Further, there is a teletypewriter printout in the "FBI notes" that indicates the airliner reported it was "23 DME miles south of Portland", or something like that, and the teletypewriter printout was time stamped (which is the time someone pressed the send button) at 8:22 PM.  While the airliner probably didn't have its tail pointed directly to the Portland VORTAC, it was still traveling away from there at the rate of about 3 DME miles per minute.  This means that the DME counter would only display "23" for about a 20 to 25 second period.

Other information in the "George Harrison Papers" gives various times for that message.  Those times range from 8:18 to 8:22.  The 8:22 time was the time the message was sent by ARINC and it is not known if that was the initial time the message was sent or if this was a redirection of the message to NWA at Portland from somewhere else.

Based on recent discussions with highly knowledgeable people in the communications business, it would probably take some minutes for the people who received the airliner's message on the ground (ARINC) to formulate the message, type it, and then send it.  By contrast, the 8:18 time could be the time someone heard the pilot's radio message on the phone patch from ARINC.  Based on Shutter's simulations and my own analyses, the 8:18 time fits the situation much, much better.

The Harrison papers have 2 people noting the event at 8:22 and one at 8:18.  I believe they were all noting what they were all hearing on the phone patch circuit as it was happening.  ARINC was relevant only in that NWA had arranged to get the ground radio support and phone patch from ARINC, because NWA didn't have its own ground radio network south of Portland.  From 305 transmitting something, to NWA sites getting it, was practically instantaneous.  Received by a radio, routed directly to telephone.  NWA had essentially bought some hours of "company frequency" from ARINC.  Not like the transmissions on standard regional frequencies that have a lot of traffic involving multiple airlines.

I think you're wrong about there being a TTY printout about the 23DME in the "FBI notes."  There is a reference to it in the NWA incident report to the FBI.  They wrote that up with the benefit of their people having heard the comms, just like noted in the Harrison papers.

Your next post:
Quote
Keep in mind that if the airliner had speeded up, Cooper could have noticed.  And he specifically told them to maintain a constant speed.

Yes.  Still, the plot indicates they sped up.  Of course, the plot could have been displayed in an FBI office just to throw us all off.
« Last Edit: March 26, 2014, 01:26:07 AM by hom »
 

Offline hom

  • Full Member
  • ***
  • Posts: 113
Re: Flight Path And Related Issues
« Reply #146 on: March 26, 2014, 01:50:10 AM »
You are not allowed to view links. Register or Login
Looking at Hominid's map again, and assuming that the eastern two large red "x"s are points on the airliner's path, and that it flew directly from the Mayfield/Malay Intersection to the Canby Intersection, then the western two large red "x"s are probably points on the T-33's flight path.

In addition to the two eastern red "x"s, there appears to be a third red "x" on that same line and just west of the words "Williamette" and "Caution".  I think I can see both a vertical line and a horizontal line with both of them being partially obscured by the large black line that is supposed to be the airliner's flight path.  Also, I think I can see a sixth red "x" which would be the third red "x" on the western lines and it is located just slightly below the east end of the word "Wilsonville".

Indeed there is that 3rd red "+" on that same longitude.  It's one of the larger ones of the plotted points.  There's another almost as large down by the Willamette River just east of the Wilsonville circle.  A small one mostly hidden by the dark line east of the word "Tualatin."  Another mostly hidden by the dark line just west of where I added "V23" under the thin radial I added.  Another just to the left of the "Control Area" I added in white.  These are all plotted points.  The four you are referencing are mistakes that were crossed out.
 

Robert99

  • Guest
Re: Flight Path And Related Issues
« Reply #147 on: March 26, 2014, 02:10:17 AM »
You are not allowed to view links. Register or Login
You are not allowed to view links. Register or Login
Looking at Hominid's map again, and assuming that the eastern two large red "x"s are points on the airliner's path, and that it flew directly from the Mayfield/Malay Intersection to the Canby Intersection, then the western two large red "x"s are probably points on the T-33's flight path.

In addition to the two eastern red "x"s, there appears to be a third red "x" on that same line and just west of the words "Williamette" and "Caution".  I think I can see both a vertical line and a horizontal line with both of them being partially obscured by the large black line that is supposed to be the airliner's flight path.  Also, I think I can see a sixth red "x" which would be the third red "x" on the western lines and it is located just slightly below the east end of the word "Wilsonville".

Indeed there is that 3rd red "+" on that same longitude.  It's one of the larger ones of the plotted points.  There's another almost as large down by the Willamette River just east of the Wilsonville circle.  A small one mostly hidden by the dark line east of the word "Tualatin."  Another mostly hidden by the dark line just west of where I added "V23" under the thin radial I added.  Another just to the left of the "Control Area" I added in white.  These are all plotted points.  The four you are referencing are mistakes that were crossed out.

The great circle course between the Mayfield/Malay Intersection and the Canby Intersection is 180.14 degrees True, which means with respect to the grid lines or, in this case, the longitude lines.  I don't see anything relevant in your comments above. 
 

Offline hom

  • Full Member
  • ***
  • Posts: 113
Re: Flight Path And Related Issues
« Reply #148 on: March 26, 2014, 01:26:30 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
Looking at Hominid's map again, and assuming that the eastern two large red "x"s are points on the airliner's path, and that it flew directly from the Mayfield/Malay Intersection to the Canby Intersection, then the western two large red "x"s are probably points on the T-33's flight path.

In addition to the two eastern red "x"s, there appears to be a third red "x" on that same line and just west of the words "Williamette" and "Caution".  I think I can see both a vertical line and a horizontal line with both of them being partially obscured by the large black line that is supposed to be the airliner's flight path.  Also, I think I can see a sixth red "x" which would be the third red "x" on the western lines and it is located just slightly below the east end of the word "Wilsonville".

Indeed there is that 3rd red "+" on that same longitude.  It's one of the larger ones of the plotted points.  There's another almost as large down by the Willamette River just east of the Wilsonville circle.  A small one mostly hidden by the dark line east of the word "Tualatin."  Another mostly hidden by the dark line just west of where I added "V23" under the thin radial I added.  Another just to the left of the "Control Area" I added in white.  These are all plotted points.  The four you are referencing are mistakes that were crossed out.

The great circle course between the Mayfield/Malay Intersection and the Canby Intersection is 180.14 degrees True, which means with respect to the grid lines or, in this case, the longitude lines.  I don't see anything relevant in your comments above.

Try reading them.  The 4 plot points you're trying to make into T33 flight path WERE PLOTTING MISTAKES that were crossed out.  They were each crossed out with three to four slashes like "///" in the same color as the plot crosses, but lighter.  It appears that there are numerous plot points you're unable to see.   You need to use some kind of software that will enable you to see the detail.
 

Robert99

  • Guest
Re: Flight Path And Related Issues
« Reply #149 on: March 26, 2014, 02:04:29 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
Looking at Hominid's map again, and assuming that the eastern two large red "x"s are points on the airliner's path, and that it flew directly from the Mayfield/Malay Intersection to the Canby Intersection, then the western two large red "x"s are probably points on the T-33's flight path.

In addition to the two eastern red "x"s, there appears to be a third red "x" on that same line and just west of the words "Williamette" and "Caution".  I think I can see both a vertical line and a horizontal line with both of them being partially obscured by the large black line that is supposed to be the airliner's flight path.  Also, I think I can see a sixth red "x" which would be the third red "x" on the western lines and it is located just slightly below the east end of the word "Wilsonville".

Indeed there is that 3rd red "+" on that same longitude.  It's one of the larger ones of the plotted points.  There's another almost as large down by the Willamette River just east of the Wilsonville circle.  A small one mostly hidden by the dark line east of the word "Tualatin."  Another mostly hidden by the dark line just west of where I added "V23" under the thin radial I added.  Another just to the left of the "Control Area" I added in white.  These are all plotted points.  The four you are referencing are mistakes that were crossed out.

The great circle course between the Mayfield/Malay Intersection and the Canby Intersection is 180.14 degrees True, which means with respect to the grid lines or, in this case, the longitude lines.  I don't see anything relevant in your comments above.

Try reading them.  The 4 plot points you're trying to make into T33 flight path WERE PLOTTING MISTAKES that were crossed out.  They were each crossed out with three to four slashes like "///" in the same color as the plot crosses, but lighter.  It appears that there are numerous plot points you're unable to see.   You need to use some kind of software that will enable you to see the detail.

I can only see the things I have previously described.  But then, I am restricted to using my eyeballs since I don't have any sight enhancing software on my computer and don't know of any magic incantations that might be useful.  What software or incantations would you recommend?