A JetBlue jet bound for New York struck a coyote on the runway at T.F. Green International Airport in Warwick, Rhode Island, early Tuesday morning, forcing the pilot to abort the trip and return for an emergency inspection with roughly 50 passengers on board.
Nobody was hurt. The plane passed inspection. But the incident raises a question that airport operators and airlines have never fully answered: why are wild animals still wandering onto active runways at commercial airports?
JetBlue Flight 1129 was accelerating down the tarmac around 6 a.m. when its landing gear slammed into the animal. The plane kept climbing. As the New York Post reported, the aircraft reached 3,700 feet before looping back toward Providence, touching down again at 6:40 a.m. Fire crews and first responders met the plane on the ground.
Passenger Erin Drozda, who was traveling with her wife, told WPRI she felt the impact before anyone on the flight crew said a word.
"We heard a thud and then after the thud, we still took off. We were up in the air for 10-15 minutes, and then all of a sudden the captain came on and said, 'This is the flight crew. If anyone heard a thud, we hit a coyote and we are now on our way back to Providence.'"
Drozda said she and her wife didn't buy it at first.
"We thought it was a joke at first. You don't ever hear that."
After landing, passengers deplaned while maintenance crews inspected the aircraft. Drozda said they waited inside the terminal for about half an hour before being cleared to reboard. JetBlue told CBS News the decision to turn around was made "out of an abundance of caution."
The airline's statement was brief and clinical: "The flight landed safely and a full inspection was done on the aircraft with no issues reported."
FlightAware data showed the plane was back in the air by 8:34 a.m. It finally touched down at John F. Kennedy International Airport in Queens at 9:06 a.m. That's roughly three hours after the original departure. For Drozda and her wife, the delay cost them their connecting flight to Costa Rica.
No one from T.F. Green International Airport has publicly commented on how a coyote ended up on an active runway.
This incident ended without injuries or serious damage. Many runway hazards don't. Readers may recall the deadly collision at LaGuardia when an Air Canada jet struck a fire truck on the runway, killing two people. In the aftermath, investigators found a flight attendant still strapped to her seat hundreds of feet from the wreckage. That disaster prompted hard questions about ground-level airport safety, questions that remain unresolved.
A coyote is not a fire truck. But the underlying problem is the same: something was on a runway that shouldn't have been, and the crew had no warning before impact. At takeoff speed, even a mid-sized animal can damage landing gear, engines, or hydraulic lines. A bird strike forced the famous "Miracle on the Hudson" landing in 2009. The margin between a funny anecdote and a catastrophe is thinner than most travelers realize.
Wildlife strikes at U.S. airports are not rare. The FAA has tracked them for decades. Airports are supposed to maintain wildlife hazard management plans. Fencing, habitat modification, and active patrols are standard tools. When a coyote reaches an active runway at a commercial airport serving a major metro area, something in that system failed.
JetBlue's statement checked the expected boxes. Safe landing. Full inspection. No issues. What it didn't address is what went wrong on the ground before takeoff, or what the airline expects the airport to do about it.
Drozda described the aftermath plainly:
"We got off the plane and stayed inside for about another half hour or so, and then they told us that everything was OK and we were able to get back on the plane."
She and her wife lost their connection to Costa Rica. Fifty passengers had their mornings upended. The crew handled the situation well, turning the plane around, getting it inspected, and resuming the flight within a couple of hours. That's competence under pressure, and the pilot and first responders deserve credit.
But competent response after the fact doesn't excuse the lapse that created the hazard. JetBlue confirmed the coyote strike and safe return, yet neither the airline nor the airport has explained how the animal got onto the runway in the first place. That silence is its own kind of answer.
Concerns about runway safety at major airports have surfaced repeatedly. A pilot warned months before the LaGuardia crash that conditions at that airport were growing dangerous. Those warnings went unheeded until people died.
Nobody died in Rhode Island on Tuesday. The coyote's fate went unreported. Passengers got to New York late. The plane checked out fine. It would be easy to treat this as a quirky travel story, a funny line from the cockpit, a startled couple missing their vacation flight.
But airports exist to move people safely through some of the most hazardous seconds in commercial travel: takeoff and landing. Every runway incursion, animal, vehicle, or debris, is a potential disaster that didn't happen yet. The FAA, airport authorities, and airlines all know this.
When the system works, a coyote on a runway is a punchline. When it doesn't, it's a headline no one wants to write.
Fifty passengers found out Tuesday morning that the gap between the two is about the width of a landing gear strut. Someone at T.F. Green ought to explain how a wild animal got that close to a loaded jet, before the next thud isn't so easy to laugh off.
