Sign up for Scenic Six
Navigate the endless possibilities of New England travel with Boston.com.
By Kristi Palma
A JetBlue flight reportedly hit a coyote during takeoff at Rhode Island T.F. Green International Airport on Tuesday.
The Airbus A320, destined for New York’s JFK International Airport, turned around “out of an abundance of caution” and returned to the Warwick airport so a maintenance crew could check the plane, according to JetBlue.
According to the flight tracking service FlightAware, the flight took off at 6:16 a.m. and landed back at T.F. Green Airport at 6:40 a.m.
“We were up in the air for about 10-15 minutes and then all of a sudden the captain came on and said, ‘This is the flight crew. If anybody heard that thud, we hit a coyote,'” Erin Drozda from Woonsocket told WBZ-TV.
Drozda told the news station that passengers deplaned for an inspection after police and EMS boarded the flight to check for injuries.
JetBlue provided the following statement about the incident:
On Tuesday, March 24 JetBlue flight 1129 with service from Providence (PVD) to New York (JFK) returned to Providence out of an abundance of caution following a report of contact between the aircraft’s landing gear and wildlife on the runway while taking off. The flight landed safely and a full inspection was done on the aircraft with no issues reported. The flight later continued to JFK without further incident.
After the plane was checked and cleared, it took off at 8:23 a.m. and landed at JFK International Airport at 9:06 a.m. An airport spokesperson told WBZ-TV that the runway remained open and the incident did not impact other flights.
Kristi Palma is the travel writer for Boston.com, focusing on the six New England states. She covers airlines, hotels, and things to do across Boston and New England. She is the author of the award-winning Scenic Six, a weekly travel newsletter.
Navigate the endless possibilities of New England travel with Boston.com.
Stay up to date with everything Boston. Receive the latest news and breaking updates, straight from our newsroom to your inbox.
Be civil. Be kind.
Read our full community guidelines.To comment, please create a screen name in your profile
To comment, please verify your email address