Delta Flight DL2307 Operating to Bismarck Diverts Back to Minneapolis

Delta Air Lines Flight DL2307, an Airbus A220-100 operating from Minneapolis to Bismarck, diverted and returned to Minneapolis-Saint Paul on August 8.

The Core Transit Update

Regional air connectivity between Minnesota and North Dakota experienced an operational change on August 8, 2026. Delta Air Lines Flight DL2307, scheduled to operate from Minneapolis-Saint Paul International Airport (MSP) to Bismarck Municipal Airport (BIS), diverted back to its departure gateway instead of completing its flight.

The service was operated utilizing an Airbus A220-100 regional narrow-body aircraft, registered as N122DU. The aircraft departed MSP at approximately 18:30 local time (following a brief delay from its scheduled 18:15 departure slot) and returned to origin safely. The official reason for the return has not been confirmed by Delta or the Federal Aviation Administration (FAA).

Flight Timetable & Aircraft Specifications

Planning domestic transits through major Midwestern US airports requires tracking flight timeline parameters and aircraft registrations. The following tables outline Flight DL2307's operational specifications and timeline milestones.

Flight Indicator	Operational Specification	Transit Metric / Value
Flight Identifier	Delta Air Lines DL2307	Non-stop domestic scheduled service
Aircraft Registration	N122DU	Airbus A220-100 (twin-jet)
Departure Hub	Minneapolis-Saint Paul International (MSP)	Scheduled pushback on August 8, 2026
Intended Destination	Bismarck Municipal (BIS), North Dakota	Key regional airport link
Diversion Outcome	Returned to Origin (MSP)	Landed safely at departure terminal
Scheduled Flight Time	~1 hour and 30 minutes	Under standard airway conditions

Flight DL2307 return-to-origin specifications.

Flight Event Milestone	Recorded Time Stamp (August 8, 2026)	Primary Location Zone	Operational Context
Scheduled Departure	18:15	Minneapolis-Saint Paul (MSP)	Planned timetable time
Actual Departure Run	18:30	MSP Runway corridor	Commenced takeoff roll
Diversion Touchdown	—	MSP Runway corridor	Returned to origin safely

Recorded timeline metrics for the return-to-origin flight.

Traveler Logistics Guide

From a ground-level perspective, the best way to navigate this is to stay at the airline's hub terminal at Minneapolis-Saint Paul (MSP) to coordinate alternate arrangements rather than attempting to self-book third-party flights, as MSP serves as a major Delta hub with extensive backup crews, spare aircraft, and customer service desks in Concourse C and G. Checking flight status screens is recommended.

To plan your transit under disruption:

Delta Mobile Rebooking: Open the Fly Delta app immediately to check if the carrier has placed you on the next scheduled flight to Bismarck. Under standard policies, Delta will handle rebooking and bag transfers automatically.
Overnight Hotel Accommodations: If the next available flight to North Dakota is delayed until the following morning, request a hotel voucher at the Delta customer service desk before leaving the secure airside zone.
Baggage Claim Queries: For luggage tracking, provide the baggage agent with your digital N122DU flight receipt, as the airline's scanning system tracks the location of bags in real time.
Alternate Highway Driving: If your travel needs are urgent, renting a vehicle at MSP is a viable alternative. The drive from Minneapolis to Bismarck takes approximately 6 hours along Interstate 94 West.

Infrastructure Impact Assessment

The route between Minneapolis-Saint Paul and Bismarck represents a key transit link for business and leisure travel between Minnesota and North Dakota. As the primary non-stop carrier on this corridor, Delta manages daily passenger flows that connect Bismarck with the wider global network via MSP.

A return-to-origin diversion highlights the flexibility of MSP's operations, where maintenance facilities and replacement aircraft are readily available to minimize travel disruptions and keep safety protocols in place.