757 Heavily Damaged In Newark Landing Mishap

Gemini Sparkle

Key Takeaways:

  • A United Boeing 757-200 experienced a "hard landing" at Newark Liberty Airport, bouncing and porpoising, causing severe damage to its nosegear which was partially pushed into the cabin.
  • The aircraft, carrying 166 people, may be written off as a result of the incident, which occurred during a strong headwind.
  • All passengers and crew disembarked safely, but the brief closure of the airport led to over 100 flight delays and cancellations.
See a mistake? Contact us.

The runway incident that briefly closed Newark Liberty Airport is now being termed a hard landing that may have written off the United Boeing 757-200 involved. The aircraft was on a flight from Denver with 166 people on board when it bounced on landing and porpoised, coming down hard on the nosegear, according to the Aviation Herald. The nosegear was partially pushed into the cabin. The aircraft came to rest with the gear still on pavement on the left side of Runway 22L and did not “skid” off the runway as was initially reported. At least four tires on the mains were flattened but the two on the heavily damaged nosegear held.

The wind was right on the nose at 15 knots gusting to 22 at the time of the incident at 12:56 p.m. local time. The passengers and crew got off the plane using stairs and were bussed to the terminal. The airport reopened quickly but more than 100 flights were either delayed or cancelled because of the incident. United has not commented on the mishap. The 757 was formerly operated by Continental before the two airlines merged under United’s name.

Russ Niles

Russ Niles is Editor-in-Chief of AVweb. He has been a pilot for 30 years and joined AVweb 22 years ago. He and his wife Marni live in southern British Columbia where they also operate a small winery.
Sign-up for newsletters & special offers!

Get the latest stories & special offers delivered directly to your inbox

SUBSCRIBE

Please support AVweb.

It looks like you’re using an ad blocker. Ads keep AVweb free and fund our reporting.
Please whitelist AVweb or continue with ads enabled.