You are viewing an obsolete version of the DU website which is no longer supported by the Administrators. Visit The New DU.
Democratic Underground Latest Greatest Lobby Journals Search Options Help Login
Google

Reply #89: Eastern Daylight Time vs. Central Daylight Time [View All]

Printer-friendly format Printer-friendly format
Printer-friendly format Email this thread to a friend
Printer-friendly format Bookmark this thread
This topic is archived.
Home » Discuss » Topic Forums » September 11 Donate to DU
Make7 Donating Member (1000+ posts) Send PM | Profile | Ignore Tue Apr-12-05 01:30 AM
Response to Reply #21
89. Eastern Daylight Time vs. Central Daylight Time
From http://www.ntsb.gov/Publictn/2000/AAB0001.htm:

... According to ATC radio transmissions, the flight departed MCO about 0919 EDT bound for DAL. At 0921:46 EDT, the flight contacted the Jacksonville Air Route Traffic Control Center (ARTCC) and reported climbing through an altitude of 9,500 feet to 14,000 feet.

At 0921:51 EDT, the controller instructed N47BA to climb and maintain FL 260. N47BA acknowledged the clearance by stating, "two six zero bravo alpha." At 0923:16 EDT, the controller cleared N47BA direct to Cross City and then direct to DAL. N47BA acknowledged the clearance. At 0926:48 EDT, N47BA was issued instructions to change radio frequency and contact another Jacksonville ARTCC controller. N47BA acknowledged the frequency change.

At 0927:10 EDT, N47BA called the Jacksonville ARTCC controller and stated that the flight was climbing through an altitude of FL 230. At 0927:13 EDT, the controller instructed N47BA to climb and maintain FL 390. At 0927:18 EDT, N47BA acknowledged the clearance by stating, "three nine zero bravo alpha." This was the last known radio transmission from the airplane. The sound of the cabin altitude aural warning was not heard on the ATC recording of this transmission.

At 0933:38 EDT (6 minutes and 20 seconds after N47BA acknowledged the previous clearance), the controller instructed N47BA to change radio frequencies and contact another Jacksonville ARTCC controller. The controller received no response from N47BA. The controller called the flight five more times over the next 4 1/2 minutes but received no response.

About 0952 CDT, a USAF F-16 test pilot from the 40th Flight Test Squadron at Eglin Air Force Base (AFB), Florida, was vectored to within 8 nm of N47BA. About 0954 CDT, at a range of 2,000 feet from the accident airplane and an altitude of about 46,400 feet, the test pilot made two radio calls to N47BA but did not receive a response. About 1000 CDT, the test pilot began a visual inspection of N47BA. There was no visible damage to the airplane, and he did not see ice accumulation on the exterior of the airplane. Both engines were running, and the rotating beacon was on. He stated that he could not see inside the passenger section of the airplane because the windows seemed to be dark. Further, he stated that the entire right cockpit windshield was opaque, as if condensation or ice covered the inside. He also indicated that the left cockpit windshield was opaque, although several sections of the center of the windshield seemed to be only thinly covered by condensation or ice; a small rectangular section of the windshield was clear, with only a small section of the glare shield visible through this area. He did not see any flight control movement. About 1012 CDT, he concluded his inspection of N47BA and proceeded to Scott AFB, Illinois.

About 1113 CDT, two Oklahoma ANG F-16s with the identification "TULSA 13 flight" were vectored to intercept the accident airplane by the Minneapolis ARTCC. The TULSA 13 lead pilot reported to the Minneapolis ARTCC controller that he could not see any movement in the cockpit. About 1125 CDT, the TULSA 13 lead pilot reported that the windshield was dark and that he could not tell if the windshield was iced.

About 1133 CDT, a TULSA 13 airplane maneuvered in front of the accident airplane, and the pilot reported, "we're not seeing anything inside, could be just a dark cockpit though...he is not reacting, moving or anything like that he should be able to have seen us by now."

About 1138 CDT, the TULSA 13 lead pilot stated, "my wingman is going to make a final pass and then we are going to head back to the tanker." The TULSA 13 wingman reported, "we did not get close enough to see any icing on the window due to our configuration...we did get up behind him but did not see anything." About 1139 CDT, TULSA 13 flight departed for the tanker.

About 1150 CDT, two North Dakota ANG F-16s with the identification "NODAK 32 flight" were vectored to intercept N47BA. (TULSA 13 flight had returned from refueling, and both TULSA 13 and NODAK 32 flights maneuvered in close proximity to N47BA.) About 1157 CDT, the TULSA 13 lead pilot reported, "we've got two visuals on it. It's looking like the cockpit window is iced over and there's no displacement in any of the control surfaces as far as the ailerons or trims." About 1201 CDT, TULSA 13 flight returned to the tanker again.

At 1210:41 CDT, the sound of an engine winding down, followed by sounds similar to a stickshaker and an autopilot disconnect, can be heard on N47BA's cockpit voice recorder (CVR), which recorded the final 30 minutes of cruise flight. The CVR also captured the continuous activation of the cabin altitude aural warning, which ceased at 1212:26 CDT. At 1211:01 CDT, ATC radar indicated that N47BA began a right turn and descent. One NODAK 32 airplane remained to the west, while one TULSA 13 airplane broke away from the tanker and followed N47BA down. At 1211:26 CDT, the NODAK 32 lead pilot reported, "the target is descending and he is doing multiple aileron rolls, looks like he's out of control...in a severe descent, request an emergency descent to follow target." The TULSA 13 pilot reported, "It's soon to impact the ground he is in a descending spiral." ...
Printer Friendly | Permalink |  | Top
 

Home » Discuss » Topic Forums » September 11 Donate to DU

Powered by DCForum+ Version 1.1 Copyright 1997-2002 DCScripts.com
Software has been extensively modified by the DU administrators


Important Notices: By participating on this discussion board, visitors agree to abide by the rules outlined on our Rules page. Messages posted on the Democratic Underground Discussion Forums are the opinions of the individuals who post them, and do not necessarily represent the opinions of Democratic Underground, LLC.

Home  |  Discussion Forums  |  Journals |  Store  |  Donate

About DU  |  Contact Us  |  Privacy Policy

Got a message for Democratic Underground? Click here to send us a message.

© 2001 - 2011 Democratic Underground, LLC