Originally Posted by
Airbubba
The EGWPS would have been screaming OBSTACLE, OBSTACLE PULL UP! and/or TERRAIN, TERRAIN PULL UP! with some hard to ignore visual cues on the PFD on the planes I've flown. I realize there are many modes, revisions and database options but I can't see how any EGWPS in a Triple would not see those hills rapidly rising.
I think so, too.
For a flight tracking project, I've learned how to position a camera point of view very precisely in the 3D virtual globe of Google Maps. Using the BR15 ADS-B data on FR24, I can put a camera (or cockpit) position in the Google virtual reality and simulate a cockpit view (yes, simulating! Neglecting bank angle, time of day and weather, of course).
One data point
before closest approach to Mt. Wilson would look like this:
https://www.google.de/maps/@34.21431.../data=!3m1!1e3,
using the position from the FR24 KML file, an interpolated track(turning!) of 67° (mean value between 59° and 75°) and an altitude AGL of 666 meters (FR 24 calibrated altitude 5625ft (1714m) minus Google Ground Elev of 1048 meters))
Closest point of approach, 306 meters above the ridge, now clear of the ridge.
https://www.google.de/maps/@34.21948.../data=!3m1!1e3
And a little bit earlier, over Altadena, at 4805', just starting the right turn (track 028° at that time).
https://www.google.de/maps/@34.18647.../data=!3m1!1e3
Use a modern, WebGL enabled browser to open the links (probably won't work on mobile devices).
EoD
p.s.
If you want to play with URL parameters ...
666a is camera elevation, 666 meters AGL
67h is viewing direction 67° (true)
89t is tilt angle (89=horizontal, 0=straight down/map view)
20y is camera opening angle, fixed