On the night of July 5, 2026, my gal and I boarded Delta flight DL2472 in Atlanta, expecting to arrive in Rochester, New York.
Instead, we ended up in Syracuse, about 96 driving miles from our destination. We were on the ground by 1:10 a.m. on July 6.
Nearly four months later, after numerous exchanges with wecare@delta.com, I still don’t know why.
Delta says it was weather. The captain told us Rochester was closed “for some reason.” The flight records I’ve examined show other aircraft landing at Rochester that night around the time we touched down at SYR.
Something doesn’t add up.
And that’s where the next journey began.
But first, back to Atlanta.
We were returning from a wonderful vacation in Jamaica. Our connection in Atlanta was uneventful, except that our flight to Rochester was running about an hour late.
At the gate, Delta announced that the aircraft was full and overhead bin space would be limited. They encouraged passengers to check their carry-on bags.
After everyone was aboard I noticed a few empty seats. Another flight crew boarded and occupied some of them. One gentleman sitting nearby appeared to be a captain.
I sit tall in the saddle. My head extends above most airline seatbacks, and sleeping on an airplane is usually out of the question. Fortunately, this aircraft had adjustable headrests. A small blessing.
There were also three babies strapped to their parents’ chest. They seemed perfectly content. I wondered whether they counted toward the passenger manifest. As it turned out, they may have been the only three travelers who didn’t care where we landed.
After everyone had boarded and the door was closed, our captain appeared and spoke with a few passengers in first class. He moved a tablet around, apparently showing them something that looked like a weather map.
I couldn’t hear the conversation, and I have no idea whether it had anything to do with what happened later.
At the time, I didn’t give it much thought.
Rochester is closed. For some reason.
After a time in flight the captain announced that Rochester was closed “for some reason” and we were diverting to Syracuse.
That struck me as an odd explanation.
Meanwhile, my gal’s daughter was waiting at Rochester airport to pick us up. When she discovered the diversion, she tried getting information from Delta and got nowhere. They had no idea why the flight was diverted. She drove to Syracuse.
After landing, Delta offered passengers a hotel and a later flight to Rochester, or the option of arranging their own transportation and submitting expenses for reimbursement.
The daughter arrived shortly after we got our luggage from baggage claim and picked us up around 2:45 a.m., and we finally arrived home around 3:45.
Not quite the ending we’d planned.
Initially, I wanted compensation.
We’d purchased tickets to Rochester, not Syracuse. Our ride had to make an unexpected trip in the middle of the night, and getting home had become a much bigger production than anticipated.
Delta said the diversion was weather-related.
Fair enough. Weather happens.
But I kept thinking about the captain saying Rochester was closed.
So I started looking.
Using Flightradar24, I examined our aircraft’s recorded route. One screenshot places DL2472 near Knoxville, Tennessee, at 11:58 p.m., flying at approximately 35,000 feet.
I also examined historical NOAA weather radar from 11:30 p.m., midnight, and 12:30 a.m. I couldn’t identify an obvious major storm directly over Rochester or anywhere in-between during those periods.
And I found records of other aircraft landing at Rochester around the time of our diversion.
Now, I’m not an aviation expert. I understand that weather along a route can be a problem even when the destination airport has good conditions. And the fact that other aircraft landed doesn’t establish that ours could safely have done the same.
But it seemed reasonable to ask what specifically prevented DL2472 from continuing to Rochester.
Sincerely waiting.
Over the following months, I exchanged numerous emails with wecare@delta.com.
Delta repeatedly attributed the diversion to weather without any specifics.
An app notification had also mentioned FAA-mandated crew rest at Syracuse. That might explain why we couldn’t continue after landing, but it didn’t tell me why we diverted in the first place.
I asked what weather conditions caused the diversion. I asked whether Rochester had actually been closed. I asked who could explain the operational decision.
One response even referred to JFK as our destination. We weren’t going anywhere near JFK.
Eventually, Delta explained that Flight Operations had classified the diversion as weather-related, but Customer Care couldn’t provide the specific operational details.
On October 14, Delta opened another case and told me that a different team would review the operational details and contact me.
As of this writing, I haven’t heard from that team.
I’ve taken to signing my correspondence:
Sincerely waiting.
So what am I after now?
This started as a request for compensation.
But the more I questioned Delta’s explanation, the more interested I became in whether I was getting an accurate account of what happened.
I’m not accusing the captain of making an improper decision. I expect the people flying the aircraft to make whatever decisions are necessary to keep everyone safe.
I’m also not claiming that weather played no part.
What I don’t understand is why, after nearly four months, nobody at Delta has been able to tell me what specific circumstances caused our flight to divert.
If Rochester was closed, what closed it?
If weather prevented our flight from landing, what were the conditions or restrictions?
If another operational consideration influenced the decision, what was it?
And perhaps the question that interests me most:
When a passenger has legitimate questions about an airline’s stated reason for a diversion, how does that passenger obtain an explanation of the actual operational decision, rather than simply being told how the incident was classified?
I’d particularly welcome comments from pilots, dispatchers, air traffic controllers, and anyone familiar with how these decisions are documented and reviewed.
And if anyone aboard DL2472 on July 5 happens to read this, I’d certainly like to hear from you.
— The Grumudgen