Showing posts with label 9/11 Commission. Show all posts
Showing posts with label 9/11 Commission. Show all posts

Friday, August 8, 2008

OVERWHELMING EVIDENCE FOR 9:38

PENTAGON ATTACK TIMELINE QUESTIONS PART 3: OVERWHELMING EVIDENCE FOR 9:38
Adam Larson / Caustic Logic
The Frustrating Fraud
August 7 2008
Last Updated 8/10/09


For those who see no reason to question the official time of the Pentagon attack, this post will be unnecessary. But for those confused by claims of different times, primarily 9:30-32 am, this may prove quite useful. If you're willing to learn... (sigh). Of all the times cited for the impact/explosion/whatever at the Pentagon on 9/11, one stands above as the most-cited, most-supported, and most-likely true – by this I mean, approximately, 9:38 am. Officially the explosive impact of Flight 77 is given as 9:37:45 or :46 based, it seems, on the Flight Data Recorder. In reality, the impact time is impossible to pin down exactly, but likely a bit after this, probably between 9:37:50 and :55 (see FDR section, first up). Following is a nearly-comprehensive list of the most direct evidence establishing the impact at right around that time.

1) Flight Data Recorder:
Much rhubarb has been made of the information on Flight 77’s Flight Data Recorder and how it doesn’t match the reality necessary to get it inside the Pentagon where it was said to be found. The last frame of data recorded is 9:37:44 or :45, depending on the exact file one’s looking at. While this is officially the moment of impact, the recorded values do not match those evident in the physical damage (most important – too high!) This is taken by some nitwits/liars as proof the plane didn’t hit. Another view takes this as a clue that this last data is actually NOT from the moment of impact, but a mile or more back, as the INS positioning says (it’s prone to error of about 1/2 mile I hear). Most analysts have come to this realization, though opinions differ on how far back, how much data is missing, and why (which is beyond the scope of this piece). Estimates range from 2 to 10 seconds remaining to impact at last frame, with the upper end of 8-10 seeming most likely to me, and placing impact at 9:37:50 or later. This slight variation of the “official” time alternates with it in the list below and illustrate that roughly all evidence points at a roughly 10 second time range best rounded to the minute as 9:38.

2) Radar:
We’ve always heard the radar data supported and defined this impact time, but fact is it can’t tell us exactly when, or even if, the plane impacted. The raw data of the Air Force’s 84th radar evaluation squadron (84RADES) was released in 2006 to researcher John Farmer, showing all returns from the DC area on 9/11. As I understand it, ‘blips’ are sent and returned every 12 seconds; the last three attributed to Flight 77 are at 9:36:48, 9:37:00, and 9:37:12 (see graphic at right, from Marco Bolletino’s reconstruction of the data). Before the next return, the airliner dropped below the coverage level of app.2,000 feet above ground [this altitude is passed by FDR about 9:37:18]. There is an established NEADS clock issue, known to be app. 25 seconds slow relative to other clocks in the FDR and at ATC facilities. Therefore, the last return would actually be at about 9:37:37, with impact presumably some seconds after that. This support is vague but would hint at an impact somewhat later than the official time less than ten seconds hence. On the other hand, the FDR pressure alt for 9:37:37 is 786 ft AGL, which seems too low to be just disappearing from radar. Perhaps I’m confused on the timeline discrepancy. Anyway, it’s all there… it doesn’t prove a 9:38 impact, but it fits it just fine.

1a+2a) FDR/Radar Combo:
In its Final Report, the 9/11 Commission gives the impact time of 9:37:46 [p 96], citing as its source NTSB report, "Flight Path Study-American Airlines Flight 77," created Feb. 19, 2002 by the National Transportation Safety Board. The full document in question is available in PDF form [here. The report in turn lists its sources as FDR data “as well as” (implying no conflict with) “radar data from the Federal Aviation Administration’s Air Route Traffic Control Centers, approach control at Washington Dulles Airport, and the U.S. Air Force’s 84th Radar Evaluation Squadron.” [This is the data examined above]. From this, the report summarizes that “the airplane accelerated to approximately 460 knots (530 miles per hour) at impact with the Pentagon. The time of impact was 9:37:45 AM.” Ooh! A one-second discrepancy! And both were likely a bit early, with the Commission closer it seems.

3) Arlington County Emergency System:
From Arlington County After-Action Report, and its first-hand access to emergency communications , we can see that key information was called in just before and after the 9:38 mark, and reactions followed in the next minutes, as recorded and logged as at a time generalized as 9:38. [emph mine].

“In the moments immediately before impact at the Pentagon, the Arlington County ECC began receiving 9-1-1 calls reporting a low flying airliner that seemed off the normal flight path. When the crash actually occurred at 9:38 a.m., all area communications seemed simultaneously overwhelmed. Firefighters calling the ECC couldn’t get through. Relatives of Pentagon workers found cellular and land lines jammed. Emergency traffic flooded radio channels.” [page A-34]

“Captain Steve McCoy and the crew of Engine 101 were […] traveling north on Interstate 395 [when they saw] a commercial airliner in steep descent, banking sharply to its right before disappearing beyond the horizon. At 9:38 a.m., shortly after American Airlines Flight #77 disappeared from sight, a tremendous explosion preceded a massive plume of smoke and fire. Unable to pinpoint the precise location, Captain McCoy immediately radioed the Arlington County Emergency Communications Center (ECC), reporting an airplane crash in the vicinity of the 14th Street Bridge or in Crystal City.” [page A-34]

At 9:38 a.m., a large smoke plume appeared beyond the Rosslyn skyline. Arlington County Police Corporal Barry Foust radioed the ECC that he saw an American Airlines jet crash into the Pentagon. The ECC swung into action [page A-35] […] [B]etween 9:41 a.m. and 9:43 a.m. on September 11, the ECC Administrator, Steve Souder, acting on his own initiative, contacted the Fairfax, Alexandria, and District of Columbia fire departments. He gave them identical instructions: deploy four engines, two trucks, one rescue unit, four EMS units, and a command officer to a staging area short of the Pentagon and hold them there until called forward.” [page a25]


4) C130 pilot report via FAA:
The 9/11 Commission briefly discussed the “second plane” at the Pentagon, a C-130H cargo plane dubbed “Golfer 06.” The Commission noted on page 26 of their final report:

“At approximately 9:38 A.M., the C130H aircraft reported to Reagan Airport controllers that the aircraft it was attempting to follow crashed into the Pentagon.” The source is given as “FAA audio file, Washington Tower, Tyson/Fluky Position, 9:38:52 .-M.; FAA letterhead memorandum, 'Partial Transcript; Aircraft Accident; AAL 77; Washington, DC; September 11, 2001,’ 7.

Although the two planes had crossed path just a minute before, both radar and the pilot’s own words agree that Golfer 06 was too far away to see Flight 77 itself at impact, but was close enough to see the smoke and to know where it was coming from. Certainly the impression was there from the beginning, and was only confirmed as it approached at 9:38, passing nearest to impact point at 9:39:15, after which it veered off to the north and west and continued on to witness the crash site of Flight 93 as well before reaching base in Minnesota.

5) 9:39 News Report - NBC:
Among the most solid clues to at least the general time of the attack of the Pentagon attack is in NBC News coverage of the 9/11 events. [video link - when watching the video, note that it starts at 9:12 am, so the video time is to be added to this for the real time] At perhaps 10 seconds after the 9:39 mark [26:24 video time], the newsroom interrupted its coverage to let Pentagon correspondent Jim Miklaszewski bring them their first news of something awry there. He told the nation:

"I don’t want to alarm anybody right now, but apparently - it felt, just a few moments ago, like there was an explosion of some kind, here at the Pentagon.” He explains he was on the east side of the mammoth building, opposite from the impact, so it was a big explosion. He saw no smoke from his side, inside the E ring, and didn’t know what was going on. “I just stepped out in the hallway, security guards were herding people out," he explained, meaning some time at least had elapsed. So far impact is looking to be one minute, 15 seconds before this broadcast. Sounds like “moments” to me.

6) Security video time stamps – Pentagon, Doubletree, Citgo:
Though neither the Citgo or Doubletree videos, released in 2006, shows the official time in their on-screen clocks, both timers roughly bracket it: Doubletree – 9:34:10 impact (app 3:35 behind) Citgo 9:40:36 (app 2:51 ahead)
It’s a very small sample to be conclusive, but this is what’s called a normal distribution, that sets a center point of app. 9:37:00. That’s pretty close for a sampling of two clocks, one of which also bears the default date of Jan 1 1993 [for a clue to the professionalism and precision of their deployment].
Regarding the time stamp of the Pentagon’s own CCTV gate cameras that famously captured the plane and impact, Col. Alan Scott told the 9/11 Commission in May 2003:

“The timeline on the impact of the Pentagon was changed to 9:37 -- 9:43 is the time that was reported that day, it was the time we used. And it took about two weeks to discover in the parking lot of the Pentagon this entry camera for the parking lot, which happened to be oriented towards the Pentagon at the time of impact, and the recorded time is 9:37. And that's why the timeline went from 9:43 to 9:37, because it is the best documented evidence for the impact time that we have.” [source]

It should be noted that the time stamp is not reproduced on-screen. The initial five released framed show a time of the following evening Sept 12 – much to the delight of mystery-mongers, it’s more likely the time the frames were processed and labeled “plane,” “impact,” etc… but they seem to have been recorded in the 9:37 slot on the correct day, and were in fact instrumental in setting the time initially. We find later it’s actually near the end of that minute, but still technically not 9:38.

7) Eyewitnesses:

Considering the known unreliability of eyewitness recollection, and that most people do not directly time-stamp their memories, it should not be surprising that this sector of the evidence is the least clear on the actual impact moment. Just a few of the published accounts provide useful clues, while many specifically disagree or are hopelessly vague. The oft-cited “9:30” is too common a rounding point to be taken too seriously, and it appears several times. A small sampling that are said to specifically cite something more like 9:32 were outlined in a previous post. But the sampling of five below does establish a normal distribution around the minute all other evidence is pointing at.

“It was about 9:35 […] it came from the south. […] I watched it come in very low over the trees and it just dipped down came down right over 395 into the Pentagon.” – Don Wright
“At 9:40 a.m. I was driving down Washington Boulevard (Route 27) along the side of the Pentagon when the aircraft crossed about 200 yards… in front of me.” - Donald R. Bouchoux
“At 9:35 a.m., I pulled alongside the Pentagon. With traffic at a standstill, my eyes wandered around the road, looking for the cause of the traffic jam. Then I looked up to my left and saw an American Airlines jet flying right at me.” - Vin Narayanan
“At 9:35, as we were watching this on TV, we heard over the loudspeaker “All medical personnel report to the front desk of Medical.” We did not know at that time that the Pentagon had been hit.” - Captain William B. Durm
“About 9:30 or so — I don't know the exact time, maybe quarter to 10 — we were still in the conference room, and we heard and felt the loud explosion of the plane hitting the Pentagon, and it reminded me of an earthquake.” – Lt. Col. Frank Bryceland [note: the mid-point of the range from 9:30-45 is 9:37:30.]


Update:As the brilliant JREF member Mangoose pointed out to me a while back:
I would also draw your attention to the witness account of William Paisley who posts as Pinch at JREF and who has a blog http://www.instapinch.com/.

You might want to contact him directly but he has elsewhere related that he was at Crystal Park 3, 10th floor on 9/11, and was watching NBC coverage of the terrorist attacks; when he saw Jim Miklaszewki's report at 9:39:10 he took a few steps to his office window and immediately saw a billowing, building mushroom cloud of black smoke rising up above the roofs of the buildings between his building and the Pentagon. This is pretty good confirmation that the explosion was not too much sooner than 9:39.


8) Wall clocks at the Pentagon:
In the Book Pentagon 9/11 [Goldberg, 2007] is pictured a wall clock from an office above the impact area, stopped at 9:36:27 – one minute, 25 sec behind the time in discussion. This is reasonably close and solid evidence of the general time at least.
Ironically enough, the famous 9:30-ish stopped clocks, which stand as the best (basically only) evidence for a blast at that early time, may also support the 9:38 time-frame. Non-nutty 9/11 Truther Russell Pickering decided that the low time is a case broken mechanisms as the clocks hit bottom-first after falling from their mounts, with simple gravity responsible for pulling the hands down to near bottom. He issued a challenge for anyone to take, which no 9:32 event supporters did, For one, CIT ally Mirage of Deceit (nutty) later confirmed the results (link unavailable). The pictures indicate the minute hands were somewhere past the 6, not before, but little else can be said for sure. But since everything else says it all went down at 9:38, is it not reasonable to call these a double-confirmation of that time with gravity rounding it down towards 9:30? [note: although it seems to have fallen differently and onto carpet, a similar effect could be behind the above clock’s being behind – or perhaps someone at the Pentagon actually was synched over a minute behind.]
Case Closed
So now that the 9:38 case looks strong enough to actually absorb even the best early-attack evidence, I’d like to turn to some assorted other evidence that doesn’t fit, and for shits and giggles use it to craft smtig even stupider than the 9:32 Pentagon attack meme (which CIT doesn’t even buy). Who knows, some bold Truther might just run with the 9:30-or-before scenario (oops, they already have) or the 9:25 WTC attack (no takers yet).

Monday, July 21, 2008

LOSING FLIGHT 77

July 21
The official accounts of radar/transponder tracking and communications problems with following Flight 77 tried to explain how the weaponized airliner was allowed to get within a few minutes of its target undetected. In total this has been taken by many (including myself) as an impossible or at least suspicious string of errors, allowing a third successful attack one hour into the new war. The Pentagon WAS protected by a mobile air-to-air missile defnse system, or was supposed to be, and the system failed as fighters were first alerted of the danger by a columnar smoke signal saying mission failed.

A useful new entry at 911 Myths regarding this - Losing Flight 77 - is up now to shed some light on it. I haven't really read it yet, this is just a tip-off. Calling on arguments by the relatively respectable and non-loony 9/11 Scholar Nafeez Ahmed, the 9/11 Commission Report and hearings, original interview with Colin Scoggins, and more, Mike W concludes:

Not a single one of Ahmed's arguments entirely withstands scrutiny, then. His most substantial point comes in the differing NORAD timeline, but the problems here are well-known, and Ahmed fails to provide independent confirmation to show that their version of events was correct. What's more, the NORAD tapes (released in full after Ahmed completed his book) contradict their timeline, for example clearly showing that they knew nothing of Flight 77 until after 9:30 on 9/11. And so while Ahmed claims victory, the reality is very different: the balance of evidence continues to support the 9/11 Commission timeline for Flight 77.

Additional discussion at JREF with technical input from Gumboot.

Sunday, June 1, 2008

THE FLIGHT DATA RECORDER {masterlist}

A BLACK BOX SURROUNDED BY A MOAT OF MYSTERY
Adam Larson
Caustic Logic / The Frustrating Fraud
last update 8/24/07
Last updated 3/4/08


Much Ado About... Nothing?

Much has been made recently of the reconstruction of data from Flight 77’s Flight Data Recorder, the so-called black box found at the crash scene inside the Pentagon. The "9/11 Truth" analysis of the data is largely based on the fragmentation of the supposedly coherent data in the flight data recorder (FDR) of the attack plane – different versions have appeared, between which different parameters are found to be "altered," leaving each piece neither totally false and dismissable nor totally true and acceptable. Thus they hover in a middle space to be analyzed by experts – primarily Pilots for 9/11 Truth and their expert allies. Predictably, the data as read and shared offers different answers to different questions at different times, depending it seems on the circumstance. The answers consistently challenge the official account, but fail to prvide a rational alternative, and often conflict with each other…

Various aspects of the NTSB animation based partly on the FDR are covered in my three-part video series "That Darn NTSB cartoon," compiled with notes here.

--- About the Sources ---
- The Evidence Trail - NTSB, FBI, 9/11 Commission, and the National Security Archive keeping the data under wraps, and its final revalation to the public in mid-2006.

- The FDR Specialist's Study: A closer look at the verifiably NTSB-provided FDR data.

- The CSV file

- "Three CD's: Where's Snowygrouch's DVD?" The Pilots' Transatlantic animation connection examined. Snowygrouch and the animation's first appearance. NTSB status at the time: unclear IMO, and yet...

--- Analysis ---
- Pilot X and the 440-foot gap: Altitude Questions raised by the NTSB animation

- Created in Translation: the altitude re-set NOT in the animation - where is it then? at FL018... forthcoming

- A somewhat dated but interesting analysis thread by myself and others @ Above Top Secret: Great insights, explanations, obfuscation, and fumbling with appearances by John Lear, John Doe X, and others.

- Ten Degrees From true: THE "NTSB Animation" is Flat Wrong Demonstrating that the north of the Citgo flight path shown is in fact at least 20 degrees off from the Black Box data it's supposed to be based on.

- Final Altitude: Eight Readings: At least four altitudes attributed the the FDR, compared to flyover "witnesses," and the "official story." I did forget radar accounts which place altitude by accounts of it dropping beneath their coverage just before impact. This is said to confirm the official story and probably does.

- 20 Minutes and 20 Miles from True: CSV longitudinal offset

- NTSB animation internal geography {masterlist} My most tedious chapter yet - five posts with one or two more to come.
- A Turn For The Worse: The culmination of the animation studies above: visual proof that the animation's final overlay map is rotated to about the same tune the plane appears north-of-the-Citgo.

- Csv/animation altitude discrepancy. Kind of a mess, mostly intended as a self-correction.

- CSV final plots: Using timeline seconds to determine geographic seconds.

- Missing Seconds: My Last FDR post

- Bank Notes: Draws on FDR bank/roll readings as part of a larger argument

--- My own NTSB FOIA Search ---
- News Coming A half-ass rundown of why I was finally contacting the NTSB.

- NTSB FOIA Response recieved - no discs enclosed

- NTSB's "Goebbels" and Me When I talked to the director - not important but a tad interesting

- Video: That Darn NTSB cartoon part 2 - the Authenticity Sidetrack Snowygrouch et al. and my discless response explained by me in a video.

Friday, November 9, 2007

THE ELASTIC TIMELINE

PENTAGON ATTACK TIMELINE QUESTIONS PART 1: THE ELASTIC TIMELINE
Adam Larson / Caustic Logic
The Frustrating Fraud
Nov 9 2007, 11pm
hopefully final update 11/13 1pm


An 18-Minute Error
Recently I had the minor pleasure of witnessing a notable timeline alteration regarding the collapse of the damaged Pentagon section. Still reported in some spots as occurring at 10:50 am EDT, it has generally been placed (9/11 Commission, ASCE, etc.) almost an hour earlier, at 9:57. But it turns out numerous better sources converge on a collapse time of 10:15 am – an 18 minute difference only sorted out by 9/11 researchers six years later. Notable mention in updating this must be give to Russell Pickering and LCF member Honway, whose work with time-stamped video provided evidence that unlocked the timeline mystery and soon more buried evidence was found. I’m now comfortable stating the collapse happened at 10:15, with earlier reports referring in confusion to an order issued to firefighters to evacuate the area in anticipation of collapse.

A 5-Minute Error
Not that such minutiae was or is very important to most, but a similar shift had happened with the more important impact time attributed to Flight 77, but that story changed five minutes backward and did so early in the game. Despite CNN having first broadcast about an explosion at the Pentagon at 9:39, in the days after the attack, the essential official story was an impact at 9:43 and generally taken as fact. Some examples: 9:40 graphic - 9:45 graphic - 9:43 CNN - 9:43 Patriotic site - 9:43 Christian Science Monitor - 9:43 CBS - 9:43 still repeated in 2007 - Etc…

It was only on September 18, a week after the attack, that NORAD announced a revised crash time of 0937(estimated) [1]. It’s not clear what this was based on, but NORAD were suspected by some of fudging it back to minimize the delay of defense indicative of a stand-down. However Col. Alan Scott, a NORAD officer active on 9/11, told the 9/11 Commission in May 2003 the time was shifted first due to an “entry camera for the parking lot, which happened to be oriented towards the Pentagon at the time of impact, and the recorded time is 9:37. And that's why the timeline went from 9:43 to 9:37, because it is the best documented evidence for the impact time that we have.” [2]. He also noted “it took about two weeks” to find this footage, so NORAD’s source as of 9/18 might have been something else. The 9/11 Commission accepting this time is often cited as evidence it was a lie, but one also supported by the Flight Data Recorder, the last frame of data at 9:37:45 (alternately rounded to 9:37 or 9:38). The radar record (see below) also supports this time, as do the NORAD tapes, and other points to be addressed in part 4.

9:43 Event Evidence Addressed
I spent a long time digging for all reports I could find for reasons 9:43 was first offered as Flight 77's crash time, and found almost no evidence at all directly indicating it. One possible exception is longtime CT researcher,founder of 9/11 Citizen's Watch, and DC resident John Judge, who later offered Paul Thompson ’the Flight 77 timeline’: “a 9:41 crash time into the Pentagon. I still say it was later, but certainly not at the 9:37 NORAD claims (and shouldn't they know?). I put it at 9:43 earliest, 9:48 latest, but maybe my clock is off. I did hear it hit and looked at the time.” [4] Earlier he'd explained that from his home in DC, 1/2 mile away, he heard a blast loud enough to shake his windows. [3]

A secondary explosion, like the ones widely reported by ear-witnesses, is one likely explanation for Judge's timeline. A few examples: “Two explosions, a few minutes apart, prompted me to start walking.” “Those fleeing the building heard a loud secondary explosion about 10 min. after the initial impact.” “secondary and third-order explosions started going off. One of them was a fire department car exploding.” On-site news reporters and others compiled by Arabesque back this up. At least one powerful blast with erupting fireball was photographed by Daryl Donley within a few minutes of the attack (above - note this fireball is erupting as the area is already damaged and smoldering. Ralph Olmholt found a source somewhere indicating "jetting flame from an underground utility bunker, presumably a broken gas main" was said to be responsible for Donnely's "dramatic picture," a theory he doesn't seem to buy. [4]

This harrowing account by survivor Kevin Shaeffer, originally published in Shipmate magazine, and re-posted 9/11/02 at Citizen Smash/Indepundit, seems to support the original time:

“In a flash, at exactly 9:43 a.m., the entire Command Center exploded in a gigantic orange fireball and I felt myself being slammed to the deck by a massive and thunderous shock wave. It felt to me as if the blast started with the outer wall facing my backside, blowing me forward toward Commander Dunn’s desk. I never lost consciousness, and though the entire space was pitch black, I immediately sensed that I was on fire.” [5]

I'm not enough of an explosives expert to say if an orange fireball moving inward in the building and igniting him is indicative of any type of explosives package, but it does fit the profile of jet fuel hurtling inward. So this would seem more likely to be the initial impact than the 9:43 blast of what seems to be burning fuel moving outward. Whether he was watching the actual time and had seen it turn to 9:43 just before the event, or filled it in later based on the flawed initial reports is not clear.

It could be the loudest explosion was the one at 9:43, louder than the crash itself – loud enough it shook Judge’s windows a half-mile away – while for whatever reason he didn’t hear the earlier crash. Other DC residents may have heard the same thing, triggering a rash of calls taken as the most likely point just due to this noise factor - it was likely flawed intelligence echo chambered in the initial confusion that got the first timeline off by five minutes. It was probably not a sinister cover-up.

Or was it a cover-up? If the secondary explosion were, for example, engineered for some reason, as some have speculated, there would be reason for them to say that was the hijacked jet crashing. Hmmm.... Discussion at the Loose Change Forum was inconclusive on the cause of the explosions, although member Honway provided this highly relevant screen cature:
Gaffney’s 9:43 Cover-Up Evidence
Another possible reason for a cover-up has been offered by Mark Gaffney, a noted environmental and peace activist and published expert and author on ‘Gnostic Secrets.’ He wrote a seminal piece posted at Rense.com called The 9/11 Mystery Plane, regarding the E4B ‘doomsday plane’ seen and filmed over the Capitol. There at about the time of the attack across the Potomac, this airborne command center is thought by some to have been running the remote control for the Pentagon attack plane. As worthy as this analytical piece is, Gaffney followed it with The 9/11 Mystery Plane Part II: Did the US Military Fudge the 9/11 Timeline?

Still eschewing overt silliness in favor of a relatively even keel, it elaborates on reports of the mysterious white jet over or near DC’s restricted airspace around 9:40-9:45, and alleges official flight path misinformation (vague at best) to allow us to believe this was Flight 77 before impact. Supporting this is live CNN footage from 9/11, where White House correspondent John King reported around 09:52 "about 10 minutes ago, there was a white jet circling overhead.” Gaffney summarizes “I believe that the US military announced the original 9:43 AM Pentagon crash time to conceal the presence of the E-4B over Washington.” [7]

However, recently released 84 RADES data, viewable here in stunning video form with Air Defense audio, shows nothing over DC at 9:43. An aircraft labeled “M3_0310” crosses just north of DC, flying west, at about 9:46-9:46:40, heads north then loops back south passing east of DC around 9:49. The E4B is also said to have passed the capitol twice, so it seems blip M3_0310 that skirts that airspace is this same craft.

This data must be approached with the proper caution due all evidence, but so far I see no particular reason to doubt it aside from its conflicts with 'CIT-compliant' eyewitnesses. But regarding this separate craft, if this is accurate and represents the white plane, it would seem King was rounding up when he said it passed the mall ‘ten minutes ago.’ Interestingly, its takeoff time – from Andrews Air Force Base - as seen in the video is 9:43:43, so if true it would have been on the ground at the official impact time as well as the 9:43 window. If this jet truly did not pass until 9:46, placing the impact time three minutes prior would have been a silly and risky gambit. This radar data has never been seen until now, but the cover-up might at any point have been exposed by any class of data: 911 calls, other call records, time-stamped video, etc. Or alternately, if other evidence supports Gaffney's claims, then the RADES data might be shown altered to conceal the true time of its flight.

Back Six More?
The RADES video linked to above also shows Flight 77 disappear from radar just short of the Pentagon at 9:37:12; this is consistent with its final dive to official impact 33 seconds later, and one more point of evidence that the shift from 9:43 to 9:38 was justified. But a sporadic attempt at another shift back of six minutes in the impact/explosion time - to about 9:32 – has been afoot for a while now and seems to have a lot of evidence backing it. Is it time for me to shift the timeframe back another six minutes, or is it not? This is my main reason for delving into timeline questions and the case for a ‘9:32 event,’ supported in part by Gaffney, will be introduced in the next post and its points of evidence directly addressed in the following one.

Sources:
[1] North American Aerospace Defense Command. “NORAD’s Response Times.” News release. September 18 2001. Accessed via: http://www.standdown.net/noradseptember182001pressrelease.htm
[2] National Commission on Terrorist Attacks Upon the United States. Second Public Hearing, panel 1. May 23, 2003.Hart Senate Office Building, Room 216, Washington, DC. Witness: Col. Alan Scott (Ret.). http://www.911commission.gov/archive/hearing2/9-11Commission_Hearing_2003-05-23.htm
[3] Judge, John. The Pentagon Attack and American Airlines Flight 77. February 21 2004. http://www.ratical.org/ratville/JFK/JohnJudge/PAandAAF77.html
[4] Olmholt, Ralph. "The Dog Should Have Barked." Pentagon Reasearch.com. December 22 2004? ('date created' in html info) http://www.pentagonresearch.com/098.html
[5] Account of Kevin Shaeffer. Shipmate magazine. Original URL (non-funtioning): http://www.usna.com/News_Pubs/Publications/Shipmate/2002/09/Ring.htm. Accessed via: http://www.indepundit.com/archives/2002_09.html
[6]
[7] Gaffney, Mark H. The 9/11 Mystery Plane (Part II): Did the US Military Fudge the 9/11 Timeline? Rense.com. July 5, 2007. http://www.rense.com/general76/wdb.htm

Saturday, August 25, 2007

BARBARA HONEGGER

THE PSYCHIC MUNCHKIN BEHIND THE HOLY GRAIL
Adam Larson
Caustic Logic/The Frustrating Fraud
December 15 2006


Perhaps the oddest case in the small but fertile world of government functionary-9/11 Truth crossover is that of Barbara Honegger, a dedicated but elusive and little seen 9/11 warrior with murky roots (apparently military and intelligence). She was allegedly into weird parapsychic stuff, channeling voices of supercomputers from the future and whatnot, [1] before she went to work in the late 1970s for a rising star named Martin Anderson at the Hoover Institute (where he remains as a Senior Fellow). She then followed Anderson to the White House as an assistant to join the Reagan-Bush transition team in 1980. Anderson advised Reagan on everything from foreign intelligence to education, finance, and arms control, probably worked for Bush sr., and during the Clinton Years focused on teaching classes at Stanford (home of the Hoover Institute and where Condi Rice was briefly provost). Anderson was later an advisor to George W. Bush in his 2000 presidential campaign, [2] and eventually became a member of Rumsfeld’s influential Defense Policy Board in 2001. [3]

Honegger_White_House
Muchkin Honegger smiling with Reagan and Bush in the White House.
Honegger herself had split off from her Republican benefactors early; she only served the Reagan White House as a researcher and policy analyst until she resigned in 1983 under unclear circumstances – either over sexual discrimination or something else. In May 1985 Newsweek ran a piece on Honegger titled “The Munchkin's Musical” that stated “White House aides began whispering that Honegger was a believer in ESP who claimed she'd ridden on Halley's comet.” [4]

At the time she was also among the first to have leaked details of the “October Surprise” scandal, much of which was later verified by numerous involved parties. The deal was allegedly made by George Bush and William Casey to delay the release of the hostages in Iran - a delay that cost Carter the White House and gained it for Reagan and Bush. [5] Her charges culminated with the 1989 book “October Surprise,” predating Gary Sick’s work of the same name (which does not mention her) by two years. In the end, the scandal cost Reagan nothing, covered up by an investigation headed by a certain Lee Hamilton, who would go on later to 9/11 Commission and Iraq Study Group fame. Honegger later left a small mark on the Iran-Contra scandal, carried out as it was by largely the same networks responsible for the October Surprise, continuing to weave a picture of Bush-centered intrigue.

Despite all this, she not only remained alive but went on to tie Bush's son and former Defense Secretary in with carrying out 9/11, her works on which carry the disclaimer "all of Honegger’s research and publications on September 11 are solely in her capacity as a concerned private citizen and do not imply official endorsement." This is because in 1995 she was given a cushy job as Senior Military Affairs Journalist at the Naval Postgraduate School, which she holds till the present, writing about such things as a cyber-defense exercise in 2002: “all the National Security Agency’s Trojan horses and Air Force and Army’s info-warriors couldn’t break through the cyber walls erected by the Naval Postgraduate School’s ace “Blue” Team,” she wrote. [6] How ironic then that what some suspect of being NSA Trojan horse 9/11 arguments should have eventually broken through her psychic shields and into her research.

Honegger’s role in the 9/11 Truth movement is huge and will perhaps go down as her crowning achievement, for good or ill. Her legacy here is centered on revealing to Mike Ruppert inside info on the War Games of 9/11 which scrambled the defense and were probably co-ordinated by a Maestro working for Dick Cheney. These revelations formed what Ruppert called “in my opinion – the holy grail of 9/11 research,” and a key point for the smarter edge of the movement at large. [7] Her credentials thus seem solid, but her later works I’ve seen are sloppy and full of holes and leaps. In October 2004 she reportedly told a forum in Los Angeles that “shoe bomber” Richard Reid was really Osama bin Laden, who apparently dyed his hair, trimmed his beard, removed a few wrinkles and turned himself in as it were by trying to ignite his shoes on a trans-Atlantic flight. [8]

Honegger’s later works include "The Pentagon Attack Papers," published as an appendix in Jim Marrs’ “The Terror Conspiracy,” 2006, taking her squarely into this blog's turf. In her Pentagon analysis, she argued against a big plane and for a traditional bombing. This, she's certain, happened at 9:32, with anything happening at the official time of 9:37 being some sort of cover – possibly the impact of “an airborne object significantly smaller than […] a Boeing 757.” She cites a mixed bag of evidence, from hard fact like a stopped clock to repeated government “slips” to irrelevant coincidences, and has cited war games at the Pentagon that morning, which are unverifiable but likely incorrect. [9] (I will post on this theory in more detail sometime soon).

She has also tied the alleged original pilot of Flight 77 before it was hijacked, Captain Charles Burlingame, to “a Task Force that drafted the Pentagon's emergency response plan on what to do in case a plane hit the building.” She appears to be the source of the similar charge laid out in Loose Change, second edition’s opening segment. It’s an intriguing possibility, but it doesn’t help her tentative case that she then finds it “extremely likely, if not certain - that this 'task force' that […] Burlingame was part of was
the Cheney counterterrorism preparedness task force, and that the Pentagon plane pilot, therefore, directly knew and even worked with/for Cheney.” [10] Maybe that parapsychic training is helping her to fill in the gaps with right-brain impulses or insights from the future that make it all make sense…

No more promising is her citation of “the already legion evidence that Flight 77 did not hit the Pentagon:" “the small hole in the west side of the Pentagon being not nearly large enough for the plane’s fuselage, let alone wing width," "no damage to the lawn where Flight 77 allegedly struck and skidded before hitting the building," "wrecked plane parts at the site identified as being from an A-3 Sky Warrior, a far smaller plane than that of Flight 77, a Boeing 757.” [11] Of course my debunkings are legion as well, or getting there. "The small hole" - the unmarked lawn - the plane parts - The A3 Sky Warrior Theory.

While her reputation in the movement is generally sterling and I don’t know enough to cast large stones, these aspects of Honegger’s works – her unexplained leaps, need to tie Cheney in personally, and especially disagreeing with me over the Pentagon evidence - are deeply flawed. Whatever her intentions, she has served as a useful and strangely credible-seeming source, and also a comet-riding psychic moonbat in the employ of the US military pushing among the worst 9/11 theories. That doesn't prove anything but it's worth considering.

Sources:
[1] http://www.mindcontrolforums.com/mindnet/mn202b.htm
[2] “2001: Mr. Hoover Goes to Washington?” Myszewski, David. Stanford Review. Volume XXV, Issue 6: January 2001
http://www.stanfordreview.org/Archive/Volume_XXVII/Issue_7/2001/
[3] Martin Anderson: Keith and Jan Hurlbut Senior Fellow. http://www.hoover.org/bios/anderson
[4] Source lost... I'll check at the library and get back...
[5] http://www.spartacus.schoolnet.co.uk/JFKhonegger.htm
[6] Honegger, Barbara. “NPS Aces Second Annual DoD Cyber Defense Exercise.” http://www.nps.navy.mil/PAO/Internal/Cyber_Defense.htm
[7] Ruppert, page 336.
[8] Propaganda Patterns: Official Stories, Limited Hang Outs, Best Evidence, Distracting Disinformation
a political map of political collapse and possibilities. http://www.oilempire.us/propaganda.html
[9] Honegger, Barbara. “THE PENTAGON ATTACK PAPERS: Seven Hours in September: The Clock that Broke the Lie”
Appendix to THE TERROR CONSPIRACY by Jim Marrs. Publication date, Sept. 6, 2006 http://johnmccarthy90066.tripod.com/id206.html
[10] "War Games" by the US military on 9/11: paralysis of air defenses that ensured the success of the attacks? who coordinated these efforts?” http://www.oilempire.us/wargames.html
[11] See [9].

Friday, August 24, 2007

CSV / ANIMATION / OFFICIAL FLIGHT PATH AGREEMENT

CSV / ANIMATION / OFFICIAL FLIGHT PATH AGREEMENT
Adam Larson / Caustic Logic
The Frustrating Fraud
August 24 2007


A small post to tide my swarming readers over until I finish my animation geography analysis; I recently found, for what it’s worth, both the animation and the csv file seem to agree with the official story [ed - on this issue - the general flight path]. This is nothing new, of course, but barring minor variations of whatever significance, and looking at the 320-mile long swathe of land flown over by Flight 77, it’s all a remarkable fit.

Earthtools tells me the furthest point west in the official path is about 82° 44' 56” W, while the csv file records 83°06’ as the largest west number. These two numbers are off by about 21-22 minutes (no seconds recorded in the csv so exact margin cannot be determined), or about the margin they’re off by for the whole flight (explained here). So the official story and the csv file (corrected) match on lat/long readings at the furthest point west, and they also match at Dulles and the Pentagon; by being about 22 degrees apart across the board, they verify the board. As for the animation, I ignored its apparent lat/long grid appearing consistently off, and just used it to place the plane roughly at given times on its flight path (for example, just before a left turn at 8:39).

I made this map by stretching the 9/11 Commission’s flight path map w/state borders to fit a larger map of those borders. I then recreated the path (a bit rough in the curves) for greater clarity. I set the lat/long grid lines beneath it with Earthtools. Along the flight path, I marked 19 timed locations at key times. These were first plotted visually according to the animation, and then fine-tuned with the csv file (west corrected).

Note the remarkable, if not exact, correlation of all these data sets. The plots are off by a few minutes here and there, but on the scale of this 320-mile long swathe it all generally lines up. This is not surprising of course, as the Commission’s map and the official story in general have always relied on the flight path first downloaded we’re told within days of the attack. Just take this as another verification that the official data all lines up on the big picture flight path issue, and another excuse for me to publish a cool new graphic.

Monday, July 16, 2007

A SLOW ZOOM ON THE FINAL LOOP

A SLOW ZOOM ON THE FINAL LOOP
Adam Larson / Caustic Logic
The Frustrating Fraud
July 16 2007
last updated July 19


Connecting the Dots
The initial flight path of hijacked Flight 77, as published in the days after the attacks, was largely a connect-the-dots approach. With no transponder after the terrorist takeover, and, we were told, “limited primary radar coverage” along the attack route, the return flight was not seen for a half-hour until it entered Washington airspace with its own radar. [1] The dotted line estimations published at this point sowed among the first seeds of suspicion over the attack. Was there a swap out there in the blind spot? As more evidence comes to light, all these paths have proven broadly accurate in that the 757 headed west, turned south over the WV-KY-OH border area, lost transponder, and returned, heading East straight to the Pentagon. Of the three maps above, Newsweek’s is the most accurate. USA Today’s path has a pronounced hump giving it a submarine profile, and Time’s map has the plane swooping north on its way back, crossing its outbound flight path, twisting the loop into an infinity symbol.

The final line of the journey as it passed east of its origin at Dulles, seems from here uneventful. But in these same early days reports surfaced of a tight, controlled, implausible loop over eastern Virginia, thought by many beyond the reported skills of the alleged hijacker Hani Hanjour. Facing the west wall, Flight 77 was said to have turned 270°-360° to hit - the west wall – oddly enough, the side just renovated to withstand bombs and impacts, largely empty, and across the building from the Defense Secretary’s Office. [more on the radar blind spot and the impact location in "From the blind spot to the empty side."]

Few if any eyewitness accounts seem to address the grand loop, since it was simply too big to have been seen by any one person – the first part of it was perhaps too high to attract much attention, but as it approached the Navy Annex and continued to lose altitude, it attracted more witnesses in its last several seconds, by which time it was going straight towards the Pentagon’s west wall. With such published accounts as the early cornerstone of our awareness of the attack, this magical loop remained largely invisible, possibly another government lie.

The overall uncertainty over 77’s approach lead many to accept this flight path as plausible to explain the final loop. It has Flight 77 flying south through DC’s restricted airspace with no White House defensive fire, headed towards Rumsfeld’s office before turning to hit the opposite side of the Pentagon, giving us the 270° turn so often cited. This map is quite wrong, understating the actual degree of turn by 60° and grossly misreading the original heading. [How this old map was arrived at and what’s wrong with it is explained separately in "the "old" 270° loop explained."]

The Radar Record
Among the too-vague early report was this from the ever-unbelievable Vice President Cheney, five days after the attack: "it entered the danger zone and looked like it was headed for the White House [...] Didn't circle it, but was headed on a track into it. [...] It turned away and, we think, flew a circle and came back in and then hit the Pentagon. And that's what the radar track looks like." [2] Five days later CBS News reported “radar shows Flight 77 did a downward spiral, turning almost a complete circle,” after which “the jetliner disappeared from radar at 9:37 and less than a minute later it clipped the tops of street lights and plowed into the Pentagon at 460 mph.” [3]

It was another month before radar specialist Danielle O’Brien, on duty at the Dulles ATC tower on 9/11, told ABC News’ 20/20 “it was an unidentified plane to the southwest of Dulles, moving at a very high rate of speed [...] I had literally a blip and nothing more.” As it headed towards the Pentagon, “it was just a countdown. Ten miles west. Nine miles west […] And it went six, five, four. And I had it in my mouth to say, three, and all of a sudden the plane turned away. In the room, it was almost a sense of relief.” But the turn continued until it was much lower and facing the same direction, after which O’Brien tersely summed up "we lost radar contact with that aircraft [...] and then the Washington National controllers came over our speakers [saying] The Pentagon's been hit.” [4]

O’Brien’s interview, aired in late October 2001, was accompanied by a radar screen graphic with a south loop of near 360 degrees off the east-bound flight as seen on radar screens. Seen briefly by millions, perhaps many thought this arc of dots just a guess or irrelevant, but in fact this same path would prove accurate and come back to bite them in the butt five years later. [Other than the red lettering, this picture is a direct screenshot from the program, viewable here.]

Official Reports: Zooming the Lump
We were only allowed a slow zoom in on what that loop actually looked like in the chain of official reports. Initial NTSB studies were kept behind closed doors, being in the FBI’s jusrisdiction and exempt from FOIA requirements. But the correct loop is there in a map from the 9/11 Commission’s Final Report, released mid-2004. Note its general agreement with early reports, and also the little lump of ink on the south side of the terminal tip – that’s the final loop, unreadable in this bold line on an unnecessarily zoomed back map. This line is apparently taken from the NTSB’s Flight Path Study, made from FDR and radar data in February 2002, classified at the time but available to the commission and cited in the endnotes. The report explained how at "5 miles west-southwest of the Pentagon," Flight 77 "began a 330 degree turn." [5]

That document was finally released via numerous FOIA requests in August 2006 and posted online from numerous angles. Finally we see a zoom in on the mysterious grand loop [see below]. First we see their overall flight path, printed big enough to show a silly little loop at the end [blue box], and also a detail of the loop all on its own page, faded yellow on a pale orange topo map [red box]. This is labeled in the report as “DC area flight path,” so possibly from ATC radar track, while the overall flight path above it is said to be from the matching FDR/radar data. [6]

The Black Box
Additional Flight Data Recorder information further verifies this loop. The Specilaist’s Factual Report of Investigation (SFRI), is an NTSB documented drawing exclusively on the full Black Box readings, also released in the 2006 rush. It has all functioning parameters graphed out for the duration of the flight, spread out over 17 pages; The basics -altitude, airspeed, and magnetic heading - are reproduced on each page. Here is the clearest extraction I've taken of this, edited to show a zoomed-in final minutes reading. All lines and values are accurate according to the bars at right and left. [7]
The story it tells is that at 9:34 Flight 77 began a remarkable thhree-minute turn just short of the Pentagon. The change in magnetic heading is graphed - as it approached DC with a general heading of about 95-100° magnetic –after a slight adjustment to the north and back at 9:31-32, the plane begins its loop at 9:34 – for about three minutes it turns south and then near-full circle to the west, north, and finally settling, at about 9:37, on a northeast heading of 70° magnetic, after completing the 330° turn and descending about 4,000 feet in the process, the last 45 seconds were a straight shot at that heading and a steady descent to roughly zero altitude at 9:37:45.

Here is how to read the headings on a map - apologies for the fruit-flavored style if that offends anyone’s sensibilities. The angle and color tells headingat a given mement, tehe direction the nose is pointing. Magnetic heading, which the FDR works with, are just about 10° higher compared to headings based on geographic north, since the magnetic north pole at that time was about ten degrees west of the true north. Read zero also as 360, due north, green. Here the plane starts out deep blue – due east, roughly 90° from north, 100 mag on the FDR - and its final heading is about 60°. Add ten to get magnetic, and this is what the FDR says – 70°.

The erred NTSB working copy animation, used by Pilots for 9/11 Truth, matches as well the official loop; their “final maneuver” video starts out at 9:34:03, turn just starting, and straightening out from 9:36:45-9:37:15 The onscreen mag heading dial roughly matches the other FDR data, settling on 70 after the loop – but of course the on-screen animation somehow ends up twenty degrees off from that, which is what places it “too far to the left” to have impacted the Pentagon, as the Pilots discovered…

Sources and editing: Coming
[1] Phillips, Don. “Pentagon Crash Highlights a Radar Gap.” Washington Post. November 3, 2001. Page A06. http://www.washingtonpost.com/ac2/wp-dyn?pagename=article&contentId=A32597-2001Nov2¬Found=true
[2] "The Vice President appears on Meet the Press with Tim Russert." Camp David, Maryland. September 16 2001. http://www.whitehouse.gov/vicepresident/news-speeches/speeches/vp20010916.html
[3] "Primary Target - THE PENTAGON." CBS News. September 21 2001. http://www.cbsnews.com/stories/2001/09/11/national/main310721.shtml
[4] "`Get These Planes on the Ground' - Air Traffic Controllers Recall Sept. 11," ABC News, October 24 2001. http://web.archive.org/web/20011024150915/http://abcnews.go.com/sections/2020/2020/2020_011024_atc_feature.html
[5] National Commission on Terrorist Attacks Upon the United States. The 9/11 Commission Report. map: p. 33. Citation of Flight Path Study: Page 459, source 59 for chapter 1. Explanation of the loop on page 9.
[6] FPS
[7] Specialist’s Factual Report of Investigation: Digital Flight Data Recorder . NTSB document number: DCA01MA064 National Transportation Safety Board, Vehicle Records Division. January 31 2002. PDF download link: http://www.ntsb.gov/info/AAL77_fdr.pdf

Friday, May 25, 2007

FDR 1: THE EVIDENCE TRAIL

FDR 1: THE EVIDENCE TRAIL
Adam Larson / Caustic Logic
The Frustrating Fraud
Updated 5/23/07


Researchers curious about the Flight data recorder from the Pentagon attack plane, from 9/11 to mid-2006 anyway, were frustrated by an uncooperative government. The National Transporatation Safety Board (NTSB) Web site announced “the terrorist attacks of September 11, 2001 are under the jurisdiction of the Federal Bureau of Investigation. The Safety Board provided requested technical assistance to the FBI, and any material generated by the NTSB is under the control of the FBI. The Safety Board does not plan to issue a report or open a public docket." The FBI of course released nothing as its PENTTBOM investigation ground on, and so the data the NTSB had gleaned remained behind closed doors for years.

The data did form a partial basis of the 9/11 Commission’s work. The path for Flight 77 the Commission published in mid-2004 was based on this, not that they ever explicitly said so, and reflected the official story. Oddly, the Commission never mentioned anything about Flight Data Recorder from any flight but 93, neither confirming nor denying the existence of the other three in its Final Report, even in the footnotes.

FOIA lawsuits for the entire NTSB record of 9/11 planes were finally successful in the wake of the Moussaoui trial’s conclusion in mid-2006. The National Security Archive at George Washington University announced on august 11 “the documents were released in their entirety to the National Security Archive and were received directly from the NTSB.” The “entire” catalog of info posted online at the Archive’ site that day included three types of reports:

1) Air Traffic Control recording logs: presented for all four flights
2) Flight path and altitude studies for flights 11, 175, and 77, the first two with complete paths and altitudes based on radar returns, 77’s path partially drawn-in due to a radar gap, but showing the final grand loop over Washington, as seen on Dulles radar, over a topographic map in close detail.
3) A detailed report on the Flight Data Recorder of Flight 93.

Regarding the third category of one, the archive’s announcement read in part: “in addition to the Flight Path Studies and Air Traffic Control Recording transcripts, the NTSB released a February 2002 “specialist’s factual report of investigation” on United Airlines Flight 93 based on the flight's recovered digital data recorder.” Since its cockpit Voice Recorder, the only one recovered and readable, is still under wraps, this clearly means the FDR. “According to the report, the flight recorder functioned normally,” and provided investigator with “graphic analysis of the data recovered from Flight 93.” But oddly, this release made a claim I’ve never heard explicitly elsewhere: Flight 93’s was “the only surviving recorder from the hijacked planes on 9/11.”

Wow! I knew the Black Boxes and CVRs in New York, while three of four were allegedly found but were buried and never admitted to having survived. But I had always heard that the Black Boxes were found at both Shanksville and at the Pentagon and had yielded data in both cases. But after seeing this and seeing no mention of such a study in the 9/11 commission’s report, it almost seems reasonable to ask if the FDR even survived at all.

But of course that’s not where it stands, and this is clearly just a mistake, perhaps by an intern asked to write up apiece beyond her understanding, taking Flight 77’s FDR study not being included as a sign it didn’t have one. That still doesn’t explain [i]why[/i] it wasn’t included, of course, and it is still telling.

The evidence of the recorder surviving is thick enough. Just after the 9/11 attacks, the FBI took over the crime scene, and brought in the NTSB to help locate plane parts and especially the black boxes. By about 4:00 am on September 14, the cockpit voice recorder and the FDR were found, according to CNN and other sources. According to the ASCE's Pentagon building performance Report, the FDR at least was found near the end of the plane's trajectory in ring C (see above). The recorders were turned over to the NTSB laboratory in Washington that same day, where technicians set to summoning the data within. The CVR was found to be useless, and so we had no audio directly from inside the plane, but on the 15th FBI Diretor Mueller said useful information was gleaned from the data recorder.

The 9/11 Commission had referenced this data indirectly, via the NTSB flight path study. As with the same for Flights 11 and 175, it included an altitude mapping, but while those were based on radar returns (with no FDRs “found”), flight 77’s altitude chart is listed as a readin from the FDR. Finally, I just found, the NTSB does have a site for downloading the once-elusive Specialist's Study for Flight 77 in PDF format: "Frequently Requested Items." That's one part of the story made less mysterious. [direct PDF download link]

Back to FDR Masterlist

Tuesday, April 10, 2007

PILOT X AND THE 440 FOOT GAP

FLIGHT 77 ALTITUDE QUESTIONS
Adam Larson
Caustic Logic / The Frustrating Fraud
April 9 2007
last edited 4/15 @ 9:32 pm


In mid-2006, new doubts about the five-year-old Pentagon attack were found, built right into a government-produced animated flight path of AA Flight 77. The group Pilots For 9/11 Truth (P49T) have been able to capitalize on the inherent contradictions in this CG cartoon - most notably in their January 2007 video Pandora’s Black Box Chapter Two - to somewhat convincingly suggest an entirely new flight path that in different (and often contradictory) ways, disproved the official flight path and, if correct, make the plane’s impact a steep improbability. [I'm working on more detailed posts about both sources and discrepancies]. The latitudinal aspect of the new 757 denial trajectory, the apparent flight well to the north of the official path, is one anomaly in this animation, but will be covered elsewhere. Here we’ll focus on the altitude questions, which are, no pun intended, a little over my head and the heads of others, a fact that at least one side in the debate seems to be using to its advantage.

The animated video file was based on the flight data recorder (FDR) of the doomed 757, rendered by the National Transportation Safety Board (NTSB), and released in mid-August 2006 via a FOIA request by a P49T-affiliated researcher. By August 20, P49T co-founder Rob Balsamo (aka John Doe X) had come into possession of the damning flight simulation and wrote about it at the group’s site. The final frame was key: it shows the animation stopping abruptly, as the original data supposedly did, with the plane on-screen still hundreds of feet away from the Pentagon and still far above it. Time at this location: 9:37:44, the second before the plane is supposed to have hit the building. While at that very second the CCTV camera north of the attack path was snapping a plane cruising in about five feet off the ground, the onscreen altimeter reads 180 feet. The plane in this animation could not have hit the Pentagon, at least not at the official time. It would have been several seconds late by the speed and descent rate up to that point. But it cuts there, at about the right time but quite the wrong place, and we were thus prevented a glimpse of the fly-over, the secret landing, and the safe removal of the FDR to be planted back at the Pentagon. (??) These are the gaps we must fill in to reach the "Truth."


Screenshot of the final frame: The time is ajusted to GMT, not EDT, so 13:37:44 should read as 9:37:44. The resolution here is easier to read than in the low-res video of the final maneuver available for free viewing online here

Balsamo explains: “You will notice in the right margin the altitude of the aircraft on the middle instrument. It shows 180 feet. This altitude has been determined to reflect Pressure altitude as set by 29.92 inHg on the Altimeter. The actual local pressure for DCA at impact time was 30.22 inHg. The error for this discrepancy is 300 feet. Meaning, the actual aircraft altitude was 300 feet higher than indicated at that moment in time. Which means aircraft altitude was 480 feet above sea level.” [1] This is also 440 feet above the ground. Thus “the 5 frames of video captured by the parking gate cam is in direct conflict with the Aircraft Flight Data Recorder information released by the NTSB.” [2]

As John Doe X, Balsamo has put together several long – and lonely - posts explaining this true altitude conclusion at the Pilots’ site, and apparently has been pretty aggressive in promoting and defending it elsewhere. [3] I haven’t been able to independently verify his 300-foot correction, but initially guessed it was quite possibly correct. Either way, there is a re-set protocol; from what I gather of the reason behind this, FAA regulations mandate pilots use local atmospheric pressure settings when in the lower, more crowded airspace – below 18,000 feet (FL180). Above that point they re-set to a baseline pressure setting of 29.92. On its ascent, we're told, both the animation and the other data show Flight 77’s altimeter re-set from local pressure (30.21) to 29.92 at about 8:28 am). Pandora’s Black Box shows an altitude drop at that point from 18273 to 18058, a difference of 215 feet; so a rise of perhaps 300 feet when switching back to a nearly-same presure setting on the descent seems plausible, but the corresponding, FAA-mandated re-set is not shown in the animation, and hence the cover-up.

This may not seem surprising – why would Balsamo suspect there should be such a re-set despite the change of control from FAA-certified pilot to suicide hijacker? The reason he has a problem here, and really its own problem, is the other P49T data, also obtained separately by FOIA request, indeed did show the re-set from 29.92 to 30.23. Balsamo summed up the non-animated data “show[s] the altimeter being set in the baro cor column on the descent through [18,000 feet].” [4] I’ve checked and it does. Taking that as truth, the Pilot(s) asked the government why “the animation altimeter does not show it being set?” The question was rhetorical; the answer they had already decided on was that the omission was to make a strike look somewhat less impossible; “this is a blatant cover-up to confuse the average layman in hopes no one would adjust for local pressure to get True Altitude. Too bad for them we caught it.” [5]

A member at JREF named “Anti-Sophist” who describes himself as an Air Force trained flight data expert and electrical engineer, summed up of "JDX"s 300-foot correction “if his true altitude number is correct, he is actually on to something, […but…] No one seems to agree with his "true altitude" calculation except for him.” [6] To see what effect the "cover-up" had, and to help clear up which impossible altitude seemed more likely, I looked into the Pilots’ comparative data, a CSV file for Excel, called AAL77_Tabular, where the pressure re-sets at 18,000 feet are recorded each way. This document forms the basis of my FL018 research (thread coming), but I have yet not been able to independently verify its authenticity. Oddly enough, the recorded altitude does not change at all with the adjustment and there is no meaningful discrepancy!

Ascent:
time - Hg - alt
8:27:58 30.21 17938
------------------------------ FL180
8:28:00 - 29.91 - 18015
8:28:02 - 30.21 - 18093
8:28:04 - 29.91 - 18170
8:28:06 - 29.94 - 18247
8:28:08 - 29.91 - 18324
8:28:10 - 29.92 - 18402
8:28:12 - 29.91 - 18483

Descent:
time - Hg - alt
9:24:12 - 29.91 - 18205
9:24:14 - 29.92 - 18126
9:24:16 - 30.23 - 18049
------------------------------ FL180
9:24:18 - 30.01 - 17972
9:24:20 - 30.23 - 17895

The pressure was reset at 8:28, with no 300-foot drop in altitude, and re-set on descent, again with no effect. Yet it shows essentially what the "altered" animation shows at termination: 173 feet compared to its 180. [7] So the data here shows two pressure re-sets, 302 feet at takeoff, 173 at the end. The animation shows 300 at takeoff, ONE reset, and 180 at the end. The pilots insist the data and animation match except for "the blatant cover-up" of neglecting the second re-set, turning the data's real alt of 480-ish to 180. But in reality, the animation and this CSV file match from A to Z despite the alleged cover-up and that extra 300 feet is looking like a red herring.

But even without Pilot X’s "correction," a Pentagon attack could not have occurred by a plane that far from the building, and that high, by either the CSV file or the animation. Considering this animation also shows the northern flight path that rules out this plane reaching either the Pentagon or the light poles before it, a whole slew of glitches, or perhaps some other explanation, would be required to debunk this damning NTSB-supplied animation.

One interesting tack is to compare all available sources, check their degrees of authenticity/verifiability, and then compare which comport with which and, as Sesame Street used to urge us, find “which one of these things just doesn’t belong.” There is an investigation of this underway, going very slow so far but it should be up soon.


Sources:
[1], [2] Flight Data Recorder Analysis - Last Second of Data - 09:37:44 08/20/06 http://pilotsfor911truth.org/pentagon.html
[3] John Doe X. Fdr Vertical Speed, Altimeter lag issues addressed as well. Pilots for 9/11 Truth forum: Flight Number: American 77. Posted October 15 2006, 08:41 AM http://z9.invisionfree.com/Pilots_For_Truth/index.php?showtopic=106&st=0&
[4], [5] Questions for the US Govt regarding AA77 Flight Data Recorder. Posting date unlisted
http://pilotsfor911truth.org/pentagon.html
[6] “AA77 FDR Data, Explained.” Posted by: Anti-Sophist. October 13 2006at 9:10 pm. http://forums.randi.org/showthread.php?t=66047
[7] AAL77_Tab - Excel document - downloaded from: http://z9.invisionfree.com/Pilots_For_Truth/index.php?showtopic=64&st=0&