Pentagon.spacelist.org is a subdomain of spacelist.org, which was created on 2004-06-27,making it 20 years ago.
Discover pentagon.spacelist.org website stats, rating, details and status online.Use our online tools to find owner and admin contact info. Find out where is server located.Read and write reviews or vote to improve it ranking. Check alliedvsaxis duplicates with related css, domain relations, most used words, social networks references. Go to regular site
HomePage size: 107.583 KB |
Page Load Time: 0.220667 Seconds |
Website IP Address: 162.241.252.20 |
Peru News - Today Saturday 11th of May 2024 news.deperu.com |
CSD&M 2020|Complex Systems Design & Management Conference | 11th International Conference on Complex 2020.csdm.fr |
Home - 11th EDF Project - CFATF 11edf.cfatf-gafic.org |
Pentagon Athletic Center - Home pac.whs.mil |
Localtopia - St. Petersburg's 11th Annual Celebration of All Things Local localtopia.keepsaintpetersburglocal.org |
11th Hour Escape | Corpus Christi Escape Room corpus.11thhourescape.com |
Post Pentagon Row Apartment Community | Luxury Apartments for Rent in Arlington, VA near DC | MAA postpentagonrow.maac.com |
11th Wisconsin Civil War Regiment | In This Land of Rebeldom: A Wisconsin Regiment's Four Year Journ 11wisconsinregiment.soldierstudies.org |
Pentagon City/Arlington, Virginia | Hours + Location | Extreme Pizza pentagoncity.extremepizza.com |
Home - Pentagon Library - Library Guides at Pentagon Library whs.mil.campusguides.com |
AACC Approved Methods of Analysis, 11th Edition methods.aaccnet.org |
Orlando Printing Solutions - 11th Hour Printing Solutions business.11thhourbiz.com |
Pentagon E'Lowe's lowes.pentagonsurfaces.com |
Dept of Army Pentagon ZIP code DC dept-of-army-pentagon-dc.zip-codes.biz |
The September 11th Attack on the Pentagon https://pentagon.spacelist.org/ |
Date: Tue, 14 May 2024 19:20:16 GMT |
Server: Apache |
Upgrade: h2,h2c |
Connection: Upgrade |
Accept-Ranges: bytes |
Vary: Accept-Encoding |
host-header: c2hhcmVkLmJsdWVob3N0LmNvbQ== |
Transfer-Encoding: chunked |
Content-Type: text/html |
content="text/html; charset=utf-8" http-equiv="Content-Type"/ |
content="Microsoft FrontPage 4.0" name="GENERATOR"/ |
content="FrontPage.Editor.Document" name="ProgId"/ |
Ip Country: United States |
Latitude: 37.751 |
Longitude: -97.822 |
Feel free to share your thoughts on this horrific event or send additional web links to . Within 30 minutes of two planes hitting the World Trade Center twin towers, American Airlines Flight 77 departed Dulles International Airport bound for Los Angeles. The Boeing 757 was hijacked and crashed, loaded with 10,000 gallons of fuel, at 345 mph into the west side of the Pentagon. The five-story Pentagon is made up of five pentagonal structures arranged in concentric rings. These rings surround a five-acre open courtyard and are connected by 10 spike-like corridors. The plane took out light poles in the parking lot, hit the ground just outside the outermost ring of the Pentagon, turned up on its wing, and penetrated the E ring (outermost) midway between corridors 4 and 5 as shown below. It then traveled through the D ring and into the C ring. CNN has some good footage from a security camera that captured the plane striking the ground . Diagram of the impact and damage (Graphic courtesy of The Washington Post ) Aerial view before the attack Arial view after the attack (Pictures courtesy of spaceimaging.com . Permission is granted to publish in hard copy, broadcast and electronic media, provided proper attribution is given for each and every use. Click here for terms and conditions.) Impact site All 58 passengers, four flight attendants, and both pilots on board, as well as 125 occupants of the Pentagon, died. Although the blast from the plane and the toxic gas and heat from the resulting fire killed some people in their offices near the crash site, some people working inside the Pentagon that morning did not know that a plane had hit their building. Military and civilian personnel running up and down the corridors yelling for people to get out helped to save a lot of lives. It was estimated that there were close to 2,600 people working in the Pentagon near the impact site. The fact that so many people were able to survive speaks well to the design of Pentagon. Indeed, the building received many upgrades following the Oklahoma City bombing to protect it from similar terrorist attacks. For instance, a recently completed $258 million renovation to the west wing included Kevlar-reinforced windows. Despite the impact of the plane and the fires, the damaged area did not collapse for 30 minutes, and the windows just next to the impact site remained intact, as shown below. The web of 6-by-6-inch steel columns held the structure of the outer wall of the Pentagon together. Blast-resistant windows on either side of the impact area remained intact above the second floor. (Photos courtesy of the U.S. Department of Defense) Shortly after the plane crashed into the Pentagon, the Arlington County Fire 1 Department requested aid from the District of Columbia (DC) Fire/EMS Department . Because the incident commander had a plane crash, building fire, terrorist attack, building collapse, and a crime scene all going on at once, the District dispatched a second alarm 2 assignment to the Pentagon, along with several EMS units. A little less than an hour later, Prince George’s County Fire and EMS Department (PGFD) put out a call for all volunteer and career personnel to report to their stations . Being a volunteer firefighter with Greenbelt’s Volunteer Fire Department and Rescue Squad for almost 6 years, I reported to my station. As units from DC were enroute to the Pentagon, the DC Fire Chief called back all DC fire personnel. The Chief also requested mutual aid from Prince George’s and Montgomery Counties Fire Departments to fill in at stations in the Nation’s Capital that were sent to the Pentagon. Shortly after 11:00 am, engines 3 from Greenbelt, Morningside, Kentland, and Branchville and a truck 4 from Cottage City were transferred into the District. Greenbelt’s Chief, Assistant Chief, six other personnel, and I filled in at DC Engine 8 (1520 C Street) in southeast DC. Because we were not familiar with southeast DC, an officer from Station 8 rode with us on our engine. Shortly before 12:30 pm, we ran a hazardous materials call at a local high school. Enroute to the call, we could not help but wonder if this was part of the terrorist attack. We cleared the call almost 30 minutes later. Just after 1:00 pm, the DC Fire Department’s Pentagon Command requested a third alarm. As we were heading back to Station 8 in the District, we were informed that we were being transferred to another DC fire station. Arriving at Station 8, we dropped off the officer who was riding with us. Just as we were about to leave, he ran out telling us that we were the first due on the third alarm at the Pentagon. All transferred companies from PG were placed on the third alarm. As we were driving down the freeway responding to the Pentagon, it looked like a war zone—military vehicles and busses carrying personnel, police cruisers, and Red Cross and other disaster vehicles all rushing past; helicopters in the air; and not an airplane or passenger vehicle in sight. When we arrived at the Pentagon, we stood by in the south parking lot so that we could meet with DC fire officials and review the plan of attack. The fires were still burning, and thick black smoke filled the air . Greenbelt’s Fire Chief following a fire engine from Branchville responding to the third alarm at the Pentagon (Photo courtesy of firefighting.com ) (Photo courtesy of BBC News) Because the access tunnel leading underneath the Pentagon to the inside courtyard was only 10-foot 2-inch high, many of the towers and ladder trucks that were to go to the courtyard to put water on the roof were too tall to fit through the tunnel. Therefore, some of these apparatus had their roofs cut off so that they would fit through the tunnel. While the first and second alarms were attacking the fire from the exterior of the outer ring, at 1:25 pm, the third alarm units proceeded through the tunnel into the inner courtyard. The idea was to attack the fire from inside the Pentagon, pushing it from the unburned areas back into the burnt areas. What we found when we entered the inner courtyard was unbelievable. Large groups of military and emergency room doctors were milling about waiting for survivors to be brought out of the building. Parts of the airplane and building were thrown about the courtyard and marked with evidence flags. FBI and other federal officials were walking around conducting their investigation. Members of the military were standing by at a makeshift morgue with body bags waiting for the fires to be put out so that search-and-rescue crews could go in and recover bodies of the victims. Over 35 agencies responded to the Pentagon that day. There was a lot of misinformation that moved across the courtyard, and we felt very isolated from the events that were going on outside the walls of the Pentagon — reports of thousands of civilians and 500 firefighters feared dead at the collapse of the World Trade Center towers, a plane crashing into Camp David, a bomb exploding at the State Department, and that the military had information that 50 other targets were to be hit that day. Although some believed that there was the possibility of additional terrorist attacks on the Pentagon, we knew all we could do was focus on the task at hand. Shortly after 2:00 pm, our first task was to stand by outside the B ring while the Arlington Fire Department attempted to make entry to the first floor between corridors 4 and 5. The fire was too intense and the crew quickly retreated. Around 3:00 pm, the units from Prince George’s County were then given the unenviable task of taking the first interior attack line into the C ring of the second floor of the Pentagon with the express orders to search for survivors and extinguish what fire we could. It had been determined that this was the area most likely to have survivors. If no survivors were found, extinguishing the fires would allow search-and-rescue crews to follow behind and begin to recover bodies. A 4"...
Domain Name: spacelist.org Registry Domain ID: c19e0052f9c84575a9122cdd9e9624be-LROR Registrar WHOIS Server: http://api.fastdomain.com/cgi/whois Registrar URL: http://www.fastdomain.com Updated Date: 2024-04-05T21:36:29Z Creation Date: 2004-06-27T11:18:24Z Registry Expiry Date: 2024-06-27T11:18:24Z Registrar: FastDomain Inc. Registrar IANA ID: 1154 Registrar Abuse Contact Email: legal@fastdomain.com Registrar Abuse Contact Phone: +1.6022262389 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Registrant Organization: BLUEHOST.COM, POWERFUL WEB HOSTING - 2GB DISC - 75GB TRANSFE Registrant State/Province: UT Registrant Country: US Name Server: ns1.bluehost.com Name Server: ns2.bluehost.com DNSSEC: unsigned >>> Last update of WHOIS database: 2024-05-17T21:01:31Z <<<