Aviation News, Headlines & Alerts
 
Category: <span>ExpressJet</span>

Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

ExpressJet Flight Diverts to Buffalo due to Smoke in Cockpit

ExpressJet flight EV-3968 had to divert for an emergency landing in Buffalo, New York, on August 9th.

The Embraer ERJ-145 plane heading from Chicago, Illinois, to Montreal, Canada, was diverted after smoke was noticed in the cockpit.

The plane landed uneventfully. All fifty passengers and three crew members remained safe.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

ExpressJet Flight Rejects Takeoff From Atlanta

ExpressJet flight EV-5508 had to reject takeoff from Atlanta, Georgia, on August 9th.

The Canadair CRJ-900 plane was accelerating to takeoff for Tulsa, Oklahoma, when the crew reported a blown tire and rejected takeoff.

The plane was disabled on the runway and had to be towed off.

Everyone aboard remained safe.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

ExpressJet Flight Makes Emergency Landing in Newport News

ExpressJet flight DL-5381 had to make an emergency landing in Newport News, Virginia, on July 9th.

The plane flying from Atlanta, Georgia, was on approach to Newport News when the crew reported a possible nose gear steering issue and declared an emergency.

The plane landed uneventfully. All passengers and crew members remained safe.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

ExpressJet Flight Diverts to Louisiana After Hydraulic Failure

ExpressJet flight EV-4114 had to divert for an emergency landing in Baton Rouge, Louisiana, on February 22nd.

The plane flying from Houston, Texas, to Charleston, South Carolina, was diverted due to a hydraulic failure.

The plane landed uneventfully.

Everyone aboard remained safe.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

ExpressJet Plane Rejects Take off in Canada

ExpressJet

The Canadair CRJ-900 en-route to Atlanta, Georgia, had to reject taking off due to a lavatory smoke indication.

The plane returned safely to the apron.

All the passengers were evacuated through the main door.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

ExpressJet Flight Makes Emergency Landing in Chattanooga

ExpressJetExpressJet flight EV-5583 had to return and make an emergency landing in Chattanooga, Tennessee, on September 22nd.

The plane took off for Atlanta, Georgia, but had to return shortly afterwards after the crew noticed that a nose gear door was open.

The plane landed uneventfully. Everyone aboard remained safe.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

ExpressJet Flight Makes Emergency Landing due to Fuel Imbalance

ExpressJetExpressJet flight EV-3945 made an emergency landing in Wilkes-Barre, Pennsylvania, on September 5th.

The plane heading from Newark, New Jersey, to Milwaukee, Wisconsin, was diverted after the crew reported a fuel imbalance.

The plane landed safely. Everyone aboard remained unharmed.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Expressjet Flight Makes Emergency Landing in Minneapolis

ExpressJetExpressjet flight EV-5469 made an emergency landing in Minneapolis, Minnesota, on August 28th.

The plane was flying from Pittsburgh, Pennsylvania, when the crew reported a problem with the nose wheel steering.

The plane landed safely. Everyone aboard remained unhurt.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Expressjet Plane Diverts to New York due to Smoke in Cockpit

ExpressJetExpressjet flight UA-4199,flying on behalf of United Airlines, had to divert and make an emergency landing at Greater Rochester International Airport, Rochester, New York, on August 25th.

The Embraer ERJ-145 en-route to Canada, from New Jersey, had to divert due to smoke in its cockpit.

The plane landed safely.

No one was injured.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Expressjet Plane Returns to Norfolk after Engine Failure

ExpressJetExpressjet flight EV-5419 had to return and make an emergency landing in Norfolk, Virginia, on August 11th.

The plane took off for Detroit, Michigan, but had to return shortly afterwards after the right hand engine stopped working.

The plane landed safely. All 62 people aboard remained unharmed.

The airline arranged a replacement plane for the passengers.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Expressjet Plane Returns to Jacksonville due to Engine Fire Indication

ExpressJetExpressjet flight EV-5231/DL-5231 returned and made a safe emergency landing at Jacksonville International Airport, Florida, on July 19th.

The Canadair CRJ-700 heading towards New York had to return after the crew reported an engine fire indication in its right engine.

The plane landed safely.

No injuries were reported.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Expressjet Plane Makes Emergency Landing due to Smoke in Cockpit

ExpressJetExpressjet flight EV-4296 made an emergency landing in Wichita, Kansas, on June 20th.

The plane, flying from Houston, Texas, declared an emergency due to smoke in the cockpit.

The plane landed uneventfully. There were 52 people aboard at the time; all of them remained safe.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Expressjet Flight Makes Emergency Landing due to Hydraulic Problem

ExpressJetExpressjet flight EV-5621 made an emergency landing in Newark, New Jersey, on June 12th.

The plane was flying from Detroit, Michigan, when the crew reported a hydraulic problem and requested emergency assistance.

The plane landed uneventfully. All 45 people aboard remained unharmed.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Expressjet Flight Returns to Tulsa Due to Smoke in Cockpit

ExpressJetExpressjet flight EV-3747 had to return and make an emergency landing in Tulsa, Oklahoma, on May 25th.

The plane took off for Houston, Texas, but had to return shortly afterwards after smoke was detected in the cockpit.

The plane landed uneventfully. There were 51 people aboard at the time; all of them remained unharmed.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Detroit-Bound Plane Makes Emergency Landing in Syracuse

ExpressJetExpressJet flight 5166, operating as Delta Connection, made an emergency landing at Syracuse Hancock International Airport, New York, on February 19.

The plane took off from Burlington International Airport, Vermont, and was heading to Detroit, Michigan, when the crew noticed a mechanical issue and decided to divert.

The plane landed safely. All 49 people aboard remained unhurt.

The airline arranged a replacement plane for the passengers.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

ExpressJet Plane makes Emergency Landing in Canada due to Flaps Failure

ExpressJetExpressJet flight EV-4121/UA-4121 had to make an emergency landing at Halifax Stanfield International Airport, Nova Scotia, Canada, on January 19.

The Embraer ERJ-145, en-route from Newark, New Jersey, had to be landed in emergency due to flaps failure.

The plane landed safely.

Everyone aboard remained unhurt.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Delta Airlines Flight Diverts to Corpus Christi International Airport

ExpressJetExpressJet flight 5009, operating as a Delta connection, made an emergency landing at Corpus Christi International Airport, Texas, on December 23.

The plane, heading from Monterrey, Mexico, to Hartsfield-Jackson International Airport in Atlanta, Georgia, was diverted after its air conditioning system stopped working.

The plane landed uneventfully. There were 71 passengers and 4 crew members aboard at the time; the airport reported that two passengers were given medical assistance in an air conditioned ambulance.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

AA Flight Makes Emergency Landing in Mississippi

American EagleAn American Airlines flight made an emergency landing in Meridian, Mississippi, on December 5.

The plane, operated by ExpressJet, was heading from Dallas, Texas, to Columbia Metropolitan Airport, South Carolina, when the crew reported a crack in the windshield and requested an emergency landing.

The plane landed safely. Everyone aboard remained unhurt.

The airline arranged another aircraft for the passengers.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

American Eagle Flight Diverts to Alabama due to Fuel Leak

ExpressJetExpressJet Airlines Flight 2762, operating as American Eagle, had to divert and make an emergency landing in Huntsville, Alabama, on November 11.

The flight was heading from Chattanooga Metropolitan Airport, Tennessee, to Dallas, Texas, when a passenger reported fuel leaking out of the wing, prompting the pilot to divert.

The plane landed safely. All 41 passengers and three crew members remained unharmed.

The airline arranged a replacement aircraft for the passengers.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

ExpressJet Flight Makes Emergency Landing at Montgomery Regional Airport

ExpressJetExpressJet flight 5071 made an emergency landing at Montgomery Regional Airport, Alabama, on September 18.

It is believed that the flight, en-route from Lafayette, Louisiana, to Atlanta, Georgia was diverted after the crew reported smell of smoke in the cabin.

The plane landed safely and no injuries were reported.

The flight was operating as Delta Connection.

Pressurization Problem Forces ExpressJet Emergency Landing

ExpressJetExpressJet flight 5106 had to make an emergency landing at Columbia Metropolitan Airport in South Carolina, at around 5:30 p.m. on November 19.

According to the FAA, the flight, en-route from Atlanta, Georgia to Wilmington, North Carolina was diverted, after the pilot reported pressurization problem.

The plane landed uneventfully and no one was injured.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Birds Hit 3 Planes Near Laguardia Airport

Air CanadaThree flights made emergency landings at LaGuardia Airport, New York, after they were separately hit by birds within a period of 4 hours on September 3.

ExpressJet Flight 5400 reported bird strike shortly after 7 a.m., while it was turning to land on Runway 31. In the second incident, ExpressJet Flight 5432 was hit by the birds at about 8:53 a.m. while taxiing to the ramp and after less than 3 hours, the Air Canada 706 reported bird strike at about 11:15 a.m. while it was some 12 miles northeast of the airport.

All three planes made safe emergency landings and no injuries to personnel or damage to property was reported.

The FAA is investigating the incidents.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Two Passenger Planes ‘Nearly Collided’ Midair in New Jersey Says NTSB’s Report

According to a preliminary report released by the NTSB, two passenger planes ‘nearly collided’ mid-air last month near Newark Liberty Airport, New Jersey.

The incident happened on April 24 when a Boeing 737-800 aircraft, registered to United Airlines was about to land at the airport while an Embraer ERJ145 aircraft belonging to ExpressJet flight was taking off. At about 3pm, the distance between the two planes was recorded to be only 200 feet laterally, and 400 feet vertically.

The report revealed that “The local controller recognized that the spacing was insufficient and instructed the B737 to go around. He provided traffic advisories to both the B737 and the ERJ145 pilots and instructed the ERJ145 pilot to maintain visual separation from the B737. The ERJ145 pilot responded that he was going to keep the aircraft’s nose down. The B737 overflew the ERJ145 at the intersection of runways 29/4R”.

There were 47 passengers and 3 crew members aboard the ExpressJet flight while the United flight was flying with 155 passengers and 6 crew members on board.


Warning: Trying to access array offset on value of type null in /home/airflight/www/www/wp-content/themes/fluida/includes/loop.php on line 270

Clear and Present Danger

I don’t know if we should blame George Jetson and his hover car commute to work, or Bruce Willis’s talkative flying taxi in The Fifth Element, but the fiction world (or at least the world according to movie directors) predicts a day when flying cars will endure a traffic filled commute identical to gridlock traffic that occurs on rush hour highways. It’s a completely irrational view, given the state of contemporary air traffic control. I don’t see it happening. At least, not until planes or flying cars can defy gravity and manage to hover motionless on demand, the flying car commute to work can’t happen. Not with our current protections. And that’s a good thing. The extra safety measures we have today are essential, because because gravity works. We can only hope our safety measures are adequate, or better than adequate. Just to keep from falling, physics requires that planes have to hurtle through the air at high speed to stay aloft, and require a multitude of safety measures to keep from colliding at all angles. Planes rely on pilots, of course, but also air traffic control, which is supposed to monitor plane trajectory and make certain that planes are miles apart. Commercial planes also have the TCAS (traffic collision avoidance) system which relies on on board transponders that monitor airspace around a plane, in order to avoid airborne collisions.

I have ranted before about the misnomer of the near miss. If two planes nearly collide, they nearly hit. If they almost miss (i.e. near miss), then it must have actually hit. So I dislike the term, because it doesn’t mean what it sounds like it means. I’d be happy to play around with the semantics, though, if it meant we could avoid the actual situation of planes colliding or nearly colliding. It’s a crucial thing to consider, especially since there were two near air collisions plus a collision a couple of weeks ago.

One (nearly) happened when a United Airlines San Francisco-Newark flight (155 passengers and six crew), and a Newark-Memphis ExpressJet (47 passengers and three crew) flew within 200 feet laterally and 400 feet vertically. The Expressjet was taking off; and the United pilot was ordered to abort their landing, and circle the airport but instead chose to land the plane.

The preliminary report for the United flight says that “on Thursday, April 24, 2014, about 1503 eastern daylight time, a near midair collision occurred at Newark Liberty International Airport (EWR), Newark, New Jersey, when an Embraer ERJ145, departing EWR runway 4R for Memphis, Tennessee, passed in close proximity to a Boeing 737-800 arriving from San Francisco, California, intending to land on runway 29. Both aircraft were on regularly scheduled 14 Code of Federal Regulations Part 121 passenger flights and under control of EWR airport traffic control tower (ATCT) at the time of the incident. There was no damage reported to either aircraft, or any injuries to passengers or crew.

The B737 contacted the EWR tower on the Bridge Visual approach to runway 29. The local controller instructed the pilot to follow a B717 ahead, and cleared the pilot to land on runway 29. When the B717 was on short final, the local controller instructed the ERJ145 pilot to line up and wait on runway 4R. After the B717 crossed runway 4R, the local controller cleared the ERJ145 for takeoff. At that time, the B737 was about three miles from the runway 29 threshold. The ERJ145 did not actually begin its takeoff roll until the B737 was about 1 mile from the runway 29 threshold. The local controller recognized that the spacing was insufficient and instructed the B737 to go around. He provided traffic advisories to both the B737 and the ERJ145 pilots and instructed the ERJ145 pilot to maintain visual separation from the B737. The ERJ145 pilot responded that he was going to keep the aircraft’s nose down. The B737 overflew the ERJ145 at the intersection of runways 29/4R.

According to recorded Federal Aviation Administration radar data, the closest lateral and vertical proximity was approximately 0.03 miles and 400 feet.

The preliminary report for the ExpressJet flight says that “On Thursday, April 24, 2014, about 1503 eastern daylight time, a near midair collision occurred at Newark Liberty International Airport (EWR), Newark, New Jersey, when an Embraer ERJ145, departing EWR runway 4R for Memphis, Tennessee, passed in close proximity to a Boeing 737-800 arriving from San Francisco, California, intending to land on runway 29. Both aircraft were on regularly scheduled 14 Code of Federal Regulations Part 121 passenger flights and under control of EWR airport traffic control tower (ATCT) at the time of the incident. There was no damage reported to either aircraft, or any injuries to passengers or crew.

The B737 contacted the EWR tower on the Bridge Visual approach to runway 29. The local controller instructed the pilot to follow a B717 ahead, and cleared the pilot to land on runway 29. When the B717 was on short final, the local controller instructed the ERJ145 pilot to line up and wait on runway 4R. After the B717 crossed runway 4R, the local controller cleared the ERJ145 for takeoff. At that time, the B737 was about three miles from the runway 29 threshold. The ERJ145 did not actually begin its takeoff roll until the B737 was about 1 mile from the runway 29 threshold. The local controller recognized that the spacing was insufficient and instructed the B737 to go around. He provided traffic advisories to both the B737 and the ERJ145 pilots and instructed the ERJ145 pilot to maintain visual separation from the B737. The ERJ145 pilot responded that he was going to keep the aircraft’s nose down. The B737 overflew the ERJ145 at the intersection of runways 29/4R.

According to recorded Federal Aviation Administration radar data, the closest lateral and vertical proximity was approximately 0.03 miles and 400 feet.

A second close call occurred outside of Hawaii; but the preliminary reports have not been posted yet. Proximity between United Airlines Kona-Los Angeles Flight 1205 and a westbound US Airways Jet initiated a TCAS alert on the United flight. The Los Angeles-bound United pilot took evasive action and made a steep dive to avoid a collision. TCAS (and the alert pilot) saved the day, after what appears to have been an air traffic control error on the ground in Honolulu.

All four of the planes were better off than the two planes that collided on April 27, in Port Richmond, resulting in one fatality and two injuries. A Cessna and a Hawker collided in midair over San Pablo Bay north of Brother Island off Richmond, California. The Sea Fury landed at Ione, California, and the Cessna impacted the waters of San Pablo Bay. Two occupants aboard the Sea Fury were uninjured.

The preliminary report for the Cessna indicates that a couple of days after that near accident, a collision occurred. On April 27, 2014, about 1606 Pacific daylight time, a Cessna 210E, N4962U, and a Hawker Sea Fury, N20SF, collided in flight near Port Richmond, California. Sanders Aircraft, Inc., was operating both airplanes under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The private pilot in the Cessna sustained fatal injuries; the commercial pilot and one passenger in the Sea Fury were not injured. The Cessna was destroyed during the accident sequence, and the Sea Fury sustained substantial damage to the empennage. Both cross-country personal flights departed Half Moon Bay, California; the Sea Fury departed about 1530 and the Cessna departed at an unknown time. Both airplanes were en route to Eagle’s Nest Airport, Ione, California. Visual meteorological conditions (VMC) prevailed, and no flight plans had been filed.

The National Transportation Safety Board investigator-in-charge (IIC) interviewed the Sea Fury pilot. The Sea Fury pilot stated the he and the Cessna pilot had flown their airplanes to Half Moon Bay to display them at an open house for the airport.

The pilot reported that after departure, he flew over the airport, and rendezvoused with a Beechcraft A36 Bonanza for a photo shoot over the Golden Gate Bridge in San Francisco, California. They flew several 360-degree patterns over the bridge, completed their photo work, and he set his course for the return to Ione.

While en route the Sea Fury pilot broadcast on a common frequency, and the Cessna pilot responded with his position. The Sea Fury pilot made visual contact with the Cessna, which was ahead and to his left. He broadcast to the Cessna pilot that he would pass low and to the left. The Cessna pilot responded that it would be a good picture. The Sea Fury pilot replied that probably not due to the speed differential; the Sea Fury airspeed was about 200 miles per hour. The Sea Fury pilot proceeded on a path that he thought would allow adequate separation; however, as he was passing the Cessna, he felt and heard a thump and he realized that the two airplanes had collided. He pulled up and looked over his shoulder and he observed the Cessna inverted and going down.

The Sea Fury pilot stated that he concentrated on flying his airplane, and initiated a climb, and conducted a controllability check to determine that he could control the airplane in the current configuration. He wanted to avoid populated areas, so he continued toward his home airport. While en route he contacted company personnel, who decided to fly another company airplane to meet and examine the Sea Fury’s condition. The Sea Fury pilot lowered the landing gear, and did a controllability check to include turns. He lowered the flaps, and repeated the testing. He reduced airspeed to a landing compatible speed of 130 mph, and checked controllability again. Determining that he had adequate control to land, he made a full stop landing at his home airport.

The Sea Fury is silver in color and the Cessna has blue wingtips with blue paint on the leading edge of both wings, on top of the cowling, and along the sides of the fuselage.

During the postaccident examination of the Sea Fury it was noted that the top remaining portion of the vertical stabilizer was crushed aft and down with blue paint transfer marks on the aft portion of the remaining metal. The operator reported that the missing vertical stabilizer section was about 12 inches long. The rudder had crush damage. The right elevator separated outboard of the middle hinge and about 3 feet of the elevator was missing. About 3 feet of the outboard section of the right horizontal stabilizer was missing. The outboard fracture surface was jagged and angular, and the upper surface had crushed inboard in an accordion fashion. Blue paint transfer marks and scratches were observed on the upper surface and within the folds of the metal.

The Cessna descended into San Pablo Bay, and the wreckage was retrieved on April 30. The recovered wreckage consisted of the fuselage and the engine. The left wing was not located. The propeller separated from the crankshaft, and was not located.

A similar report for the Hawker has also been published.

Flight has become commonplace, but we can not take it for granted.

A CRJ-200 Makes Emergency Landing in Montgomery

A mechanical fault in a CRJ-200 aircraft, forced it to make emergency landing at Montgomery Regional Airport.Montgomery

According to the airport spokesperson, the Delta flight connecting through Express Jet was carrying 47 passengers and was travelling from Atlanta to Montgomery. He further said that some mechanical issue was detected in one of the flaps and hence it was decided to request an emergency landing at Montgomery Regional Airport.

The plane landed at around 1:30 p.m. on Monday, March 17, 2014. All passengers and crew members exited safely.

Content not attributed to or linked to original, is the property of AirFlightDisaster.com; all rights reserved.

Site Credits