The Mountain time zone uses MST (UTC−7) during standard time and MDT (UTC−6) during daylight saving time. Knowing the shift helps make sense of schedules across U.S. cities, especially when flight crews move between regions and local clocks don’t match.

Multiple Choice

Which time zone uses MST in standard time and MDT in daylight saving time?

The Mountain time zone uses MST in standard time and MDT in daylight saving time. This zone observes Mountain Standard Time (UTC−7) during winter and switches to Mountain Daylight Time (UTC−6) in summer. The other major U.S. zones use different abbreviations for standard and daylight times (Eastern: EST/EDT, Central: CST/CDT, Pacific: PST/PDT). So the correct choice reflects the Mountain time zone.

Why Mountain Time Matters in Airline Operations

A flight can cross several states in a few hours, but the clock on a crew member’s phone won’t always tell the whole story. Airline schedules rely on local time, and a small mix-up can ripple through a day of airport arrivals, crew briefings, and passenger connections. For Breeze Airways flight attendants, as for cabin crews across the industry, knowing how U.S. time zones work is a simple but important part of understanding the rhythm of airline travel.

The Mountain Time Zone is the one that uses Mountain Standard Time (MST) during standard time and Mountain Daylight Time (MDT) during daylight saving time. MST is UTC−7; MDT is UTC−6. That one-hour shift is easy to overlook, especially when a route links cities in different zones or when daylight saving time begins or ends.

The Mountain clock: MST in winter, MDT in summer

The United States has four major mainland time zones: Eastern, Central, Mountain, and Pacific. Each has a standard-time abbreviation and a daylight-time abbreviation:

  • Eastern: EST and EDT

  • Central: CST and CDT

  • Mountain: MST and MDT

  • Pacific: PST and PDT

The letters offer a helpful clue. “S” stands for standard time; “D” stands for daylight time. The final letter identifies the zone. Mountain, then, pairs MST with MDT.

During standard time, the Mountain zone is seven hours behind Coordinated Universal Time, or UTC. When daylight saving time is in effect, clocks move forward by one hour, making the zone six hours behind UTC. A city that’s at 10 a.m. MST is at 11 a.m. MDT at the same moment of the year’s clock change.

That sounds tidy, but there’s a wrinkle: not every place associated with Mountain Time changes its clocks. Most of Arizona, for example, stays on Mountain Standard Time year-round. The Navajo Nation observes daylight saving time, while the Hopi Reservation, which is surrounded by the Navajo Nation in parts of Arizona, does not. So a route, airport, or destination may sit in the Mountain region without following the same seasonal clock shift as nearby locations. It’s a good reminder that time-zone labels describe rules, not just geography.

Why a one-hour shift matters in a cabin

Airline itineraries usually show departure and arrival times in each airport’s local time. If a flight leaves Denver at 2 p.m. Mountain Time and arrives in Los Angeles at 3:30 p.m. Pacific Time, the displayed times don’t mean the flight lasted only 90 minutes. The clocks in the two cities differ by an hour. A flight’s elapsed time is calculated separately from the local clock readings.

That distinction matters for cabin crews. A flight attendant may review a report time, a scheduled departure, a layover, and a later duty period in quick succession. Each time needs the right zone attached to it. “The briefing starts at 6:00” is less useful than “the briefing starts at 6:00 a.m. local time in Denver.” Clear wording prevents people from silently making different assumptions.

This is especially relevant when a crew member travels between cities, checks a schedule while away from home, or coordinates with colleagues based elsewhere. A phone may update automatically, but a printed document, wall clock, or message thread might not. Technology helps; it doesn’t remove the need to read the time carefully.

Local time, UTC, and the schedule puzzle

UTC is a worldwide reference point used in aviation and many other fields. It stays constant throughout the year, unlike local clocks that may shift for daylight saving time. Knowing the difference between local time and UTC can help explain why an aviation schedule or operational message may not match the time shown on a terminal clock.

For instance, 18:00 UTC corresponds to 11 a.m. MST, but to noon MDT. The UTC time stays put; the local conversion changes when daylight saving time begins. That’s why dates matter when converting between zones. A time comparison made in January may be off by an hour if someone uses it again in July without checking the seasonal clock setting.

Flight attendants don’t need to turn every schedule into a math problem. They do need to notice the details that carry meaning: the city, the date, the time zone, and whether the time is local or UTC. When anything seems unclear, checking an official itinerary or the airline’s current scheduling information is far safer than relying on memory.

Daylight saving time can make familiar routes feel different

In most U.S. areas that observe daylight saving time, clocks move forward in spring and back in autumn. The change can affect how travelers think about a route, even when the aircraft follows the same path. A trip that connects Mountain and Pacific cities may appear to have different departure-to-arrival clock times across seasons, although the aircraft’s actual time in the air has not changed by an hour.

The transition weekends deserve extra care. A clock may skip from 1:59 a.m. to 3:00 a.m. in spring, or repeat an hour in autumn. That can create confusion around early reports and overnight travel. Airline systems are designed to handle schedule changes, but people still need to pay attention to the date and the time displayed. “Tomorrow morning” can be ambiguous when a conversation happens close to midnight; a full date and local time are clearer.

There’s also a practical human side to the time change. Crew members and passengers may feel tired when their usual sleep schedule shifts. A one-hour change sounds small, yet early starts, late arrivals, and changing duty patterns can make it feel bigger. Clear time references help reduce avoidable stress when everyone is already moving through a busy travel day.

A few habits that keep time clear

A reliable way to read a schedule is to pause and identify four things: the date, the city, whether the time is local or UTC, and the current seasonal abbreviation. This takes only a moment. It also helps when reading a message from someone in another city: a time without a location can be a guess disguised as a fact.

When discussing a flight or crew event, naming the city is often the simplest fix. “Meet at 7:15 a.m. local time at the departure station” gives people more to work with than “meet at 7:15.” If a schedule uses UTC, say so plainly rather than assuming everyone has made the same conversion.

For Breeze Airways flight attendant training, time-zone literacy fits into a wider understanding of how airline operations connect people, schedules, and locations. It isn’t just a list of abbreviations to memorize. It’s a way to read the day accurately while aircraft and crews move across regions. MST and MDT are the Mountain pair; EST/EDT, CST/CDT, and PST/PDT belong to the other major U.S. zones. Once that pattern is familiar, the clock becomes less of a puzzle—and a lot easier to trust.