Criminal law, Politics, Science, Society

Dead Men Do Tell Tales (Of Rigged Elections)

Submitted by Gene Howington, Guest Blogger

If you’ve never heard of King Lincoln v. Blackwell, don’t be too surprised.  Project Censored calls the outsourcing of the 2004 Presidential elections in Ohio “one of the most censored stories in the world.”  Originally filed on August 31, 2006 in Ohio, King Lincoln Bronzeville v. Blackwell is an ongoing civil case to decide if the the Ohio Secretary of State at the time, Kenneth Blackwell, violated the Civil Rights Act (42 USC §§ 1983 and 1984) and the 1st, 13th, 14th and 15th Amendments to the Constitution by conspiring to “deprive and continue to deprive Ohioans of their right to vote and have, in fact, deprived and continue to deprive Ohioans of their right to vote by, in a selective and discriminatory manner, unfairly allocate election resources (such as voting machines), institute a system of provisional ballots, purge voter registrations, and broke the bi-partisan chain of custody ballots”.  The vote at the heart of the issue is the 2004 Presidential election where, in defiance of exit poll data, there was a sudden and unexpected shift in votes for George W. Bush.

New filings include a revealing deposition of the late Michael Connell.   Connell died shortly after giving his deposition in a small plane crash that is described as “suspicious”*.  In life, Connell served as the IT guru for the Bush family and their personal minister of propaganda, Karl Rove. Connell ran a private IT firm called GovTech that created the controversial electronic voting system that Ohio used during the election.  GovTech’s system transferred Ohio’s vote count late on election night to a partisan Republican server site in Chattanooga, Tennessee owned by a company called SmarTech. That is when the alleged vote shift happened that led to Bush’s unexpected victory.

The filing also contains a copy of the contract signed between Kenneth Blackwell and GovTech Solutions as well as a graphic architectural map of the Secretary of State’s election night server layout system.  In a possible indication that the system was designed with fraud in mind, the contracts and maps had never been made public until this filing.  The lead attorney on the case, Cliff Arnebeck, consulted with IT security expert Stephen Spoonamore about the network setup. Specifically, Arnebeck asked Spoonamore whether or not SmarTech had the ability to alter the results of the election.  “Yes. They would have had data input capacities. The system might have been set up to log which source generated the data but probably did not,” Spoonamore responded, further explaining that SmarTech would have had “full access and could change things when and if they want.”

Spoonamore went on to conclude that “SmarTech was a man in the middle. In my opinion they were not designed as a mirror, they were designed specifically to be a man in the middle.”  For those of you not computer savvy, a mirror site is like a back back-up.  It works when the main computer system fails.  In contrast, a “man in the middle” is a deliberate computer hacking setup (and a violation of U.S. wiretapping statutes) in which a third party sits in between computer transmissions where they can illegally alter or steal the data.  In an even more revealing statement by Spoonamore during the course of the e-mails with Arnebeck, he claims that he confronted then-Secretary of State Blackwell at a secretary of state IT conference in Boston.  Blackwell’s response?  “Blackwell freaked and refused to speak to me when I confronted him about it long before I met you,” Spoonamore wrote to Arnebeck.  In a previously submitted affidavit, Spoonamore testified, “The SmarTech system was set up precisely as a King Pin computer used in criminal acts against banking or credit card processes and had the needed level of access to both county tabulators and Secretary of State computers to allow whoever was running SmarTech computers to decide the output of the county tabulators under its control,” and that “…the architecture further confirms how this election was stolen.

Contrary to any contention that SmarTech’s servers operated simply as mirrors and that a system failure was behind the transfer of data to the Republican partisan firm, the late Michael Connell swore under oath that, “To the best of my knowledge, it was not a fail-over case scenario – or it was not a failover situation.”  This is also confirmed by Bob Magnan, the state IT specialist for then Secretary of State Blackwell during the 2004 election.  Magnan further claims that the control of the system was in the hands of private contractors at the time.  Magnan was unexpectedly sent home at 9 p.m. on election night.

For those of you already suspect of electronic voting and the election of 2004, these new revelations are a smoking gun and a road map to how the election in Ohio was rigged in favor of George W. Bush.  King Lincoln Bronzeville v. Blackwell may be a civil case, but this newly introduced evidence merits a criminal investigation by the Department of Justice.

What do you think?

Source: TruthOut.org

* Commenter Otteray Scribe did the heavy lifting on locating more information about the crash, which as it turns out, is not very suspicious at all.  His detailed and thorough post of the NTSB report is here. Thanks for the assist, Otteray Scribe!

~Submitted by Gene Howington, Guest Blogger

125 thoughts on “Dead Men Do Tell Tales (Of Rigged Elections)”

  1. OS,
    I saw that story and I just shook my head. The good news is that his Senators are running behind in the recall elections and I suspect that Gov. Walker will be taking a hike come January.

  2. They are at it again. Scott Walker has a new ploy to keep Democrats from voting. He just signed a new law making voter ID mandatory to prevent “voter fraud.” Then he shut down a number of DMV offices in mostly Democratic leaning districts, but increased the number of DMV employees in mostly Republican districts. Then look what happens when a mother and her son take a hidden camera into the DMV to get a voter ID. The boy is denied a card because his bank account is “not active enough.” Yes, you read that right. Rest of the story and video at the link below.

    http://www.dailykos.com/story/2011/07/26/998944/-VIDEO:-WI-DMV-Tells-Boy-His-Bank-Account-Doesn%E2%80%99t-Show-Enough-%E2%80%9CActivity%E2%80%9D-To-Get-a-Voter-ID?detail=hide

  3. @GeneH/Buddha

    “I’d ask if you realize that civil and criminal process are two distinct processes that are not predicated on the finding of the other, but clearly you don’t.”

    Stop being such an idiot with your loaded statements.

  6. Voter suppression is another one of their tactics. Look at all the laws passed by the republican legislatures and signed by their governors in 2010. Voter suppression also happened in Ohio in 2004. Blackwell was gone by 2008.

  7. Electoral shennanigans have been a hallmark GOPer electoral politics since shortly after LBJ signed the Voting Rights Act of 1965 with the result that the old slavers and segregationists of the Old South moved solidly into the GOP and brought their christianist allies with them to the Grand Old Party. I rememeber here in Orange County, California when the Prince of Orange hired armed guards to provide security at polling places here in OC that had heavy latino populations or at least latino names. None of these guards were dispatched to polling places like the Balboa Bay Club in Newport Beach or other majority anglo and GOP strongholds. Nothing much has changed over the decades since that shift occured. I suppose the inevitable questions needs to be asked: is liberty and democracy (or more correctly the march toward liberty and democracy for all) dead in this Nation. Are we being governed by fascist oligarchs? Is this Great Experiment over?

  8. You are welcome, Gene.

    We have had a couple of crashes at our local regional airport due to similar icing conditions. One of them killed NASCAR driver Alan Kulwicki. Ice and airplanes do not go well together.

  9. kderosa,

    As usual, your statement is a distortion. Saying that new evidence in a civil case merits opening a criminal investigation is not the same thing as ruling before the court has on the civil matter. I’d ask if you realize that civil and criminal process are two distinct processes that are not predicated on the finding of the other, but clearly you don’t. You should ask OJ about this. Even he knows better.

  10. You boys seem to have already ruled before the court has. That’s convenient. Will you cry that it is jury rigging if there is no liability found?

  11. OS,

    Thanks for the updated information! I was just out looking for information on the crash and you just saved me a ton of work. I’ll add a note to the story referencing this post.

  13. Gene – thats the problem. Clowns like kdreadful are only interested in furthering the interests of their masters. That means it OK if a Republican does it. Crimes can only be committed by Democrats just like terrorism can only be committed by Muslims, not by Christian white guys like Timmy McVey.

    Normal people want all criminals prosecuted, paid trolls want to pretend their masters don’t commit crimes and when they get caught the other side does it.

    Klownderosa, if this voter fraud is so wide spread how is it that there are not more prosecutions? Is every DA, every State AG, every investigator in on it?

  14. Sorry folks. As much as we might be suspicious, the crash occurred in bad weather with icing conditions. Collins apparently had a case of “get-home-itis,” which is an itch that has killed many pilots and their passengers over the years. Having accidentally flown into icing myself, it is one of the scariest things any aviator can experience. I have lost good friends to icing and in almost every case, they were simply too eager to get home.

    This report is long (sorry ’bout that), but here is the full NTSB Narrative Report. It reads like a clinic on all the things a pilot should not do.

    HISTORY OF FLIGHT

    On December 19, 2008, about 1753 eastern standard time, a Piper PA-32R-301T, N9299N, impacted terrain during a precision approach to runway 23. A post crash fire then ensued destroying the airplane. The airplane impacted the front lawn of a vacant house about two miles east-northeast from Akron-Canton Regional Airport (CAK), Akron, Ohio. Night instrument meteorological conditions prevailed at the time of the accident. The pilot was fatally injured, and there were no ground injuries. The flight departed from College Park Airport (CGS) College Park, Maryland, about 1531 and was returning to CAK at the time of the accident.

    A person representing N9299N called the Raleigh Automated Flight Service Station at 1427 to obtain a briefing. The caller stated he was trying to “figure out” when he could return to CAK and was “looking at the possibility” of a departure time of 1500. The briefer asked: “Would you like a standard briefing and just cover everything or you need to just to kind a hit the highlights ?” The caller replied: “ …I don’t want to waste your time. Let’s figure out if this sounds like a suicide mission or not, and then we’ll go from there.” The briefer then stated: “Well, I’ll hit the highlights. If there’s something else you want you just let me know.”

    The caller provided the briefer with a proposed route of flight with an altitude of 6,000 feet. The caller wanted to know if he would be low enough to be outside or above freezing rain and whether he would arrive at CAK before the weather there went from “bad to worse.” The briefer provided the caller with information from airmet sierra for general IFR conditions as well as mountain obscurations and airmet zulu for icing, which across the route of flight, was for moderate ice from the freezing level to 20,000 feet. Also, a beginning freezing level “guesstimate” was between 7,000 feet and 8,000 feet at the time of the briefing. Towards the northwest, the freezing level increased and then decreased and at the destination it was “close” to 4,000 feet to 5,000 feet. The briefer told the caller that the freezing precipitation seemed to be up toward the north and central Pennsylvania. The briefer told the caller that the radar indicated rain but did not show any frozen or mixed precipitation at the time of the briefing. The briefer stated that there were metars that showed that rain was reaching the surface and the “andrews” metar showed some unknown precipitation was reaching the surface.

    The briefer said that the computer thought that its some type of frozen precipitation, which was usually the case for unknown precipitation, but he didn’t think it was the case because of the temperature. The Akron, Ohio, forecast until 1700 was: 1 statute mile (sm) light rain, ceiling 400 feet above ground level (agl) overcast, occasionally 4 sm light rain, ceiling 800 feet agl overcast. The forecast between 1700 and 1800 was: winds 010 degrees at 10 knots, 5 sm visibility, light rain and mist, ceiling 800 agl overcast. At 1800, the forecast was: wind 010 degrees at 12 knots, 4 sm visibility, light freezing drizzle, snow, and mist, ceiling 700 feet agl, overcast. The briefer said that by 1800, the mixed or frozen precipitation would be reaching the surface and a lot of times it could be mixed precipitation. The briefer told the caller that the freezing level at the time of the briefing at Akron, Ohio, was “close” to about 3,000 – 4,000 feet but it may drop as the day progresses. The briefer said that the there was a frontal system with a cold front in western Indiana with a “couple” of low pressure areas. According to the prognostic chart, the low pressure area would be in western Pennsylvania by 1900 and the cold front would have passed through. The briefer said that the temperatures could decrease “fairly quickly.” After the briefing, the caller filed a flight plan without an alternate airport.

    The briefing ended about 20 minutes after it began. The caller asked several questions regarding the weather throughout the briefing. The pilot then departed on the flight about 45 minutes after receiving the briefing.

    According to Federal Aviation Administration (FAA) event summaries, N9299N departed from CGS about 1531 and was in contact with Potomac Terminal Radar Approach Control (TRACON) for the initial part of the flight. N9299N was subsequently handled by Washington Air Route Traffic Control Center (ARTCC), Cleveland ARTCC, and Pittsburgh TRACON before being handed off to CAK TRACON. The flight appeared to be uneventful, except that at 1642, in response to a Cleveland ARTCC request for flight conditions, the pilot reported encountering “moderate chop.”

    At 1736:19, the CAK Air Traffic Control (ATC) Tower, local controller, instructed the pilot to fly heading 340 degrees for radar vectors to the instrument landing system (ILS) 23 final approach course, which was acknowledged by N9299N. At 1742:34, the local controller instructed N9299N to descend and maintain 3,200 feet. N9299N acknowledged the clearance, and asked if there were any pilot reports of icing below 6,000 feet in the area. The controller responded that there were no reports of icing, but asked the pilot to advise if he encountered any. At 1749:42, the controller transmitted that N9299N was two miles northeast of the EGGII outer marker (the EGGII outer marker is about 5.7 nautical miles from runway 23), instructed N9299N to fly heading 250 degrees to intercept the localizer and maintain 3,200 feet until established, and issued a clearance for the ILS 23 approach, which was read back by N9299N at 1749:52. At 1751:04, N9299N was told to contact CAK tower.

    The pilot contacted CAK tower at 1751:16, and was cleared to land on runway 23. The controller also advised N9299N that it was left of the localizer, and N9299N replied, …correcting.” At 1752:31, the tower controller transmitted, “… you’re still well to the left of the localizer sir would you like to go back around for the approach.” At 1752:37, N9299N replied “…please repeat.” The tower controller repeated that N9299N was “…still well to the left of the localizer would you like to go back around for the approach.” N9299N replied, “…nine nine November we’d like to correct.” The tower controller responded, “roger… two and a half miles from the field cleared to land runway 23 for nine nine.” The pilot acknowledged the landing clearance. At 1753:02, N9299N transmitted, “…uh can we do a three sixty and uh reestablish ourselves.” The controller responded that he was unable to approve the request, and instructed the pilot to climb and maintain 3,000 feet. The controller asked the pilot for his present heading, and the pilot responded that he was heading “due north and climbing.” The controller replied, “… no delay in the climb, climb and maintain 3000.” The pilot did not respond. At 1753:47, the controller transmitted, ” nine two nine nine November did you copy.” At 1753:50, N9299N transmitted, “nine nine November declaring an emergency oh [expletive].” The controller responded, “November nine nine November maintain altitude the airport is two miles west of you.” The pilot did not respond. There was no further contact with the aircraft.

    According to the National Transportation Safety Board ATC Group Chairman Factual Report, radar plots of N9299N show comparative plots with other aircraft that had flown the ILS 23 approach. These plots depict N9299N as being above and to the left of the approaches flown by the other aircraft.

    A witness reported that he was outside of his home when he first heard a “loud” engine sound from a small aircraft. The sound was coming from the north and sounded as though the pilot was trying to accelerate “rapidly.” Suddenly, the witness saw two bright lights coming almost nose first toward the ground with the engine “roaring.” Based upon the witness’ view of the lights, he assumed the airplane was flying west to east. He lost sight of the airplane when it descended below a tree line.

    PERSONNEL INFORMATION

    The pilot held a private pilot certificate with a single-engine land rating that was issued on June 18, 2004, after he had accumulated a total flight time of 86 hours. On June 19, 2006, he was issued an instrument airplane rating after he had accumulated 282 hours of flight time. A Piper PA-32 airplane was used for the instrument airplane rating examination. According to the pilot’s Airman Medical Certificate application dated October 19, 2007, he reported a total flight time of 510 hours, of which 50 hours were accumulated in the past 6 months. Remains consistent with a pilot’s logbook were found in the wreckage but damage to the logbook precluded documentation of total and recent instrument flight experience.

    The pilot had no previous history of accidents, incidents, or enforcement actions.

    AIRCRAFT INFORMATION

    The 1997 Piper PA-32R-301T, serial number 3257018, airplane was registered on August 21, 2007, to the Sierra-November Aviation Inc, of which was a corporation the pilot was the president. The airplane was powered by a Textron Lycoming TIO-540-AH1A engine, serial number L-9879-61A and was equipped with a Hartzell three-blade controllable pitch propeller, HC-13YR-1RF, serial number HK182A. According to the FAA Type Certificate Data Sheet, the airplane’s maximum rated engine/propeller speed was 2,500 rpm.

    According to maintenance logbook entries, the engine was overhauled and then installed on November 24, 2004, at an aircraft total time of 1,344.2 hours and a Hobbs time of 1,344.2 hours. The last annual inspections of the airplane and engine were both dated July 24, 2008, at a Hobbs time of 1,727.6 hours.

    The airplane was equipped with an auxiliary electrically driven vacuum pump. The airplane was not equipped with an anti-ice/deice system and according to the airplane flight manual was not approved for operations in icing conditions.

    METEOROLOGICAL INFORMATION

    The National Weather Service (NWS) Surface Analysis Chart for 1900 showed the accident site was located west of an occluded front and in the vicinity of a low pressure trough. Station models north of the low pressure and frontal systems indicated an extensive area of clouds and precipitation in the form of snow, freezing rain, and drizzle. Surrounding that area was an area of marginal visual flight rules (MVFR) conditions the extended over most all of Ohio and Pennsylvania, and Virginia. The closest visual flight rule conditions were depicted without a contour line over extreme southern Ohio and West Virginia, to the south of the accident. MVFR and IFR conditions prevailed along the route and the accident site. The station models in the vicinity of the accident site depicted IFR to MVF condition with overcast ceilings between 400 and 1,100 feet above ground level (agl).

    The weather depiction chart for 1700 depicted an area of IFR conditions by a shaded contour line extending north of the warm front across Maryland, Delaware, New Jersey, parts of southern and northern Pennsylvania, New York, and portions of Ohio along the trough of low pressure.

    The closest upper air data was from the NWS, Pittsburgh, Pennsylvania, located about 60 miles east-southeast of the accident site at an elevation of 1,224 feet mean sea level (msl). The 1900 sounding indicated several shallow temperature inversions were noted below 18,000 feet associated with a front at approximately 6,000 feet and due to subsidence at 10,500 feet. The sounding had a relative humidity of 75 percent or more at the surface and between approximately 2,000 feet to 7,500 feet, with drier air aloft above the temperature inversions. The precipitable water value was 0.42 inches. The freezing level was identified at 3,906 feet msl, with the temperature profile supporting a light rain to snow mixture at the surface. The temperature and moisture structure of the sounding also supported a high probability of light snow to moderate rime icing conditions between the freezing level at 3,906 feet and 7,500 feet.

    The sounding wind profile indicated surface wind from 280 degrees at 10 knots, with little variation in height through 18,000 feet with increasing wind speeds immediately above the boundary layer, which indicated a potential for low-level wind shear and turbulence. A low-level wind maximum was identified at 4,500 feet with winds from 275 degrees at 45 knots and winds exceeding 50 knots above 7,000 feet.

    Geostationary Operations Environmental Satellite number 13 imaging depicted a radiative cloud top temperature over the accident site was observed at -5.6 degrees Celsius (C), which according to the Aircraft Meteorological Data Relay (AMDAR) Sounding over CAK indicated cloud tops in the range of 6,500 feet.

    CAK was equipped with an automated surface observation system (ASOS) at an elevation of 1,228 feet msl. CAK ASOS weather observations recorded for the following times were:

    1735: wind – 280 degrees at 9 knots; visibility – 10 miles; sky condition – broken 700 feet above ground level agl, overcast 1,400 feet agl; temperature – 1 degree C; dew point – -1 degree C; altimeter 29.77 inches of mercury.

    1751: wind – 300 degrees at 11 knots; visibility – 9 miles; sky condition – broken 500 feet agl, overcast 1,000 feet agl; temperature – 1 degree C; dew point – -1 degree C; altimeter 29.78 inches of mercury

    1809: wind – 300 degrees at 10 knots; visibility – 2 1/2 miles, mist; sky condition – overcast 400 feet agl, overcast 1,000 feet agl; temperature – 1 degree C; dew point – -1 degree C; altimeter 29.78 inches of mercury.

    Visibility continued to deteriorate and at 1815 was reported as 1 1/2 miles in mist.

    Pilot Statements Regarding Icing.

    Several pilots who operated into or out of KCAK on the day of the accident provided statements regarding the weather conditions they encountered. Their statements are summarized as follows:

    Report at 1312 – A pilot who departed in a single-engine turboprop Cessna 208B Caravan stated that he entered the clouds at 400 feet, and started picking up light, mostly clear ice, in the clouds, with tops at 6,100 feet. At 8,000 feet, he noted the temperature of 4 degrees C.

    Report at 1741 – A pilot flying a multiengine Beechcraft Baron (BE58) attempted a localizer approach to runway 25 at KAKR. The pilot went missed approach and executed an ILS runway 23 approach at KCAK. He indicated that, at 7,000 feet the temperature was between 5 to 7 degrees C, with cloud tops at 6,500 feet. The aircraft began to accumulate ice entering the clouds from 6,500 feet to the surface, and he also reported encountering rain in the clouds. At 3,000 feet, the temperature was near freezing and he encountered mixed icing, which accumulated very rapidly with 1 1/4 inches of ice on portions of the wing. He reported that he broke out of the clouds between 400 and 500 feet agl.

    Report at 1808 – A pilot flying a Cessna Citation business jet (C550) flew the approach immediately after the accident airplane. The flight diverted from Wayne County Airport (KBJJ) located approximately 20 miles east of KCAK due to low ceilings and visibility in fog. The pilot indicated the cloud tops were about 6,000 feet, and he encountered icing conditions at approximately 3,000 feet down to 400 to 500 fee. He stated that he actuated the deicing boots twice on approach. He estimated accumulating up to 1 inch of ice on the approach, and indicated a ceiling of 200 feet agl and visibility 1/2 mile.

    Report at time unknown on the evening of the accident – A pilot flying a multiengine Cessna Golden Eagle (C421) near the time of the accident reported cloud tops near 5,000 feet. The pilot stated that he descended into a solid layer of clouds and began encountering icing “right away” below 3,500 feet, with moderate rime type ice. They had difficulty with the landing gear and had increased power setting to maintain their airspeed, which they attributed to the icing conditions. The aircraft landed hard due to the amount of ice accumulation on the airplane. The pilot estimated 1 to 2 inches of ice on the unprotected areas of the airplane, and “a lot” of ice on the unprotected areas of the windshield. He indicated the ceiling heights as 500 to 600 feet and visibility 2 to 3 miles, when he landed, and he provided an icing report to the air traffic control tower’s ground controller

    WRECKAGE AND IMPACT INFORMATION

    The main wreckage of the airplane was located 40 degrees 56.025 minutes North 081 degrees 22.690 minutes West at an elevation of 1,163 feet or about 2.6 miles east northeast from the approach end of runway 23 at CAK. The main wreckage consisted of the fuselage, wings, empennage, engine, and propeller, all of which were located in the yard of a home. Damage to the home included thermal damage. Ground scarring in the yard of the home was oriented along an approximate heading of 120 degrees. The airplane came to rest in an upright position with the landing gear extended.

    Examination of the airplane revealed that the left wing sustained greater relative damage than the right wing. The empennage was attached to approximately 13 feet of the aft fuselage, which was separated from the cabin. The left horizontal stabilizer displayed greater relative damage than the right horizontal stabilizer. The outer portion of left horizontal stabilizer was separated about midspan of the attached horizontal stabilizer which exhibited inward crushing at the separation. The forward portion of the fuselage and instrument panel exhibited damage from impact forces and fire.

    The propeller and hub were separated from the crankshaft flange. Two propeller blades remained attached to the propeller hub while one propeller blade was separated from the propeller hub. One of the two propeller blades that remained attached to the hub displayed S-shaped bending.

    A separated portion of instrument panel that contained START, BATTERY, and ALTERNATOR rockers switches had the BATTERY and ALTERNATOR switches in the on position. The flight instruments were separated from the panel and/or sustained impact damage.

    Examination of the flight control system revealed no anomalies that would have precluded normal operation.

    MEDICAL AND PATHOLOGICAL INFORMATION

    The pilot was issued a third class Airman Medical Certificate on November 19, 2007, with the following limitation: “holder must wear corrective lenses when exercising the privileges of this medical certificate.” The Airman Medical Certificate application indicated “Yes” in response to “Do You Currently Use Any Medication” and noted the use of only fexofenadine/pseudoephedrine, azelastine nasal spray, and minocycline. The application also noted “yes” to “Hay fever or allergy” and indicated visits to health care providers for “adult acne” and “seasonal allergies.” No other medications or medical conditions were noted.

    An autopsy of the pilot was conducted by the Stark County Coroner on December 20, 2008.

    The FAA’s Final Forensic Toxicology Fatal Accident Report of the pilot reported that putrefaction was present and 79 (mg/dL, mg/hg) ethanol detected in muscle, 16 (mg/dL, mg/hg), and no ethanol detected in brain. Chlorpheniramine was detected in blood, liver, gastric, and heart. Pseudoephendrine was detected in liver.

    TESTS AND RESEARCH

    A Sound Spectrum Study of digital audio from approach and local control was performed by the NTSB Vehicle Recorder Division. During the 1749:52 transmission by N9299N acknowledging a clearance for the ILS 23 approach, the engine/propeller speed was 2,458 rpm. After ATC transmitted that N9299N was “…still well to the left of the localizer would you like to go back around for the approach,” N9299N made a 1752:37 transmission during which the engine/propeller speed was 2,458 rpm. During the 1753:50 transmission by N9299N declaring an emergency, the engine/propeller sound was 2,497 rpm. A review of each transmission indicated no evidence of aural cockpit warnings.

    The engine was shipped to Textron Lycoming where it underwent disassembly and examination due to impact and post crash fire damage, which precluded an engine test run. Disassembly of the engine revealed that the internal components were wetted with oil and none of the engine components and accessories displayed signatures that would have precluded normal operation.

    Post accident examination of the airplanes autopilot system and vacuum systems revealed no anomalies that would have precluded normal operation.

  15. kderosa,

    “Now the vote tallies have to comport with exit poll sampling?”

    That would be your improper inference. You seem to have a general problem with that process. Just like your improper inference that I’m a partisan. If you’re upset that your boys the Republicans got caught in this instance, I suggest you take it up with them. I’m for prosecuting criminals on a strictly non-partisan basis.

  16. Another great story Gene. Two in a row. You keep it up it might be time for your own blog.

  17. @Howington

    “The vote at the heart of the issue is the 2004 Presidential election where, in defiance of exit poll data, there was a sudden and unexpected shift in votes for George W. Bush.”

    Giggle. Now the vote tallies have to comport with exit poll sampling?

    If republicans are going to commit voter fraud, they should just do it the old fashion way the way Democrats still do it in big cities.

  18. funny about small plane crashes – Sen Carnahann, Sen. Wellstone, this guy. I’m not a believer in conspiracy theories but if I may quote Auric Goldfinger:”Once is accident, twice is coincidence, thrice is enemy action.”

  19. They, the republicans, were desperate to regain control in ’10… lots to of stuff to cover up. Lots of eyes on them too. 🙂

  20. The subversion of elections has been proven beyond a reasonable doubt in some Kentucky election cases involving judges and other officials.

    Ironically, the federal government prosecutor advanced a criminal “conspiracy theory” in the indictments.

    Conspiracy theories, they are not just for nuts any more.

Comments are closed.