Time Zone Conversion Problem: Podcast Recording & International Travel

What This Problem Teaches

• Converting between time zones using UTC as the universal reference
• Tracking date changes when crossing multiple time zones
• Adding and subtracting hours while accounting for day boundaries
• Coordinating schedules across international time differences
• Calculating travel times and arrival schedules for international flights

Visualizing the Problem

Let's create a table to organize the time zone information and track our conversions:

Solution: Method 1 — UTC Reference Point Conversion

Part (a): Finding Recording Times

Step 1 — Convert Nairobi time to UTC

The podcast records at 2:00 PM Monday in Nairobi (UTC+3). To find UTC time, we subtract the offset:

Step 2 — Convert UTC to Brisbane time

Brisbane is UTC+10, so we add 10 hours to the UTC time:

Step 3 — Convert UTC to Vancouver time

Vancouver is UTC-7, so we subtract 7 hours from the UTC time:

Part (b): Finding Flight Arrivals

Step 4 — Convert Veronica's departure to UTC

Veronica leaves Tuesday 11:00 PM Vancouver time (UTC-7). To convert to UTC, we add 7 hours:

Step 5 — Calculate Veronica's arrival in UTC

Add her 20-hour flight time:

Step 6 — Convert Bianca's departure to UTC

Bianca leaves Wednesday 10:00 AM Brisbane time (UTC+10). To convert to UTC, we subtract 10 hours:

Step 7 — Calculate Bianca's arrival in UTC

Add her 16-hour flight time:

Step 8 — Convert both arrivals to Nairobi time

Nairobi is UTC+3, so we add 3 hours to each UTC arrival:

Step 9 — Compare arrival times

Bianca arrives Wednesday 7:00 PM and Veronica arrives Thursday 5:00 AM. The time difference is:

Solution: Method 2 — Timeline Tracking with Date Changes

This method visualizes the problem on a continuous timeline, carefully tracking when days change across time zones.

Part (a): Timeline Method for Recording Times

Step 1 — Create a reference timeline

Start with the known recording time and work outward from Nairobi as our anchor point:

Part (b): Flight Timeline Method

Step 2 — Map departure times on UTC timeline

Convert both departures to the same UTC reference:

Step 3 — Calculate arrivals and convert to Nairobi time

The timeline clearly shows Bianca arrives 10 hours earlier than Veronica.

Verification

Checking Part (a)

Let's verify all three cities are recording simultaneously by converting back to UTC:

Checking Part (b)

Let's verify the flight calculations by working through Bianca's journey:

And Veronica's journey:

Common Pitfalls

The Pattern Behind This

Time zone problems follow a consistent three-step pattern:

The conversion rules are:

This pattern works for any time zone problem, whether it involves scheduling meetings, calculating flight arrivals, or coordinating international events. Always use UTC as your neutral reference point to avoid confusion about which direction to convert.

Why This Matters

Time zone coordination is essential in our globally connected world:

International Business: Companies routinely schedule video conferences across multiple time zones. A meeting at 2 PM Eastern needs to account for participants in London (7 PM), Mumbai (12:30 AM next day), and Los Angeles (11 AM).

Travel Planning: Airlines publish departure and arrival times in local time zones, but fuel planning, air traffic control, and crew scheduling all work in UTC. A flight from New York to London might depart at 10 PM local time and arrive at 9 AM local time, but that's actually a 6-hour flight, not 11 hours.

Global Events: Live streaming events like sporting matches or product launches must coordinate viewer times worldwide. The 2024 Olympics opening ceremony in Paris needed to announce start times for every country where people would watch.