> ... I looked up her flight on my calendar, and it said not 1:30, but 11.30.
Actually, it didn't say either. It said 1:30 EST and it made the visual adjustment on the calendar to show you what time that would be in Arizona, where you were.
You have to look at this from both directions.
What if this was the other way around and YOUR WIFE was looking at the calendar and saw an 11:30 am flight time? She'd be bored at the airport for two extra hours.
Let's take this a step further.... let's say her flight takes, what, 4 hours? So she enters into the calendar a 4-hour flight event starting at 1:30pm EST. You can now look at the calendar and know exactly what time you have to pick her up from the airport (around 3:30pm, allowing for a 4 hour flight and a 2 hour timezone difference). However, by your reckoning, this event should have been showing on the calendar as running from 1:30pm to 5:30pm, leaving her hanging in baggage claim for 2 hours.
Even worse would be flying the other way around, where the calendar showed 1:30PM but the flight was actually leaving at 11:30am. You'd end up at the airport after the flight has left, and the airlines aren't going to compensate you for missing the flight because you misread the calendar.
I think it's unreasonable for everyone to have an intrinsic knowledge of the time of an event in some far-flung (or even adjacent) time zone (especially in Arizona which has a different DST schedule from the rest of the country), and to know the intent of the person who created the event. Do you really know the location where whoever added the event to a calendar was at the time? The local time is far more important for most users.