B737-300 range/speed

Updating status to: Awaiting Feedback

Can you post a screenshot of your Add Flights page (with frequencies selected) so I can see the calculated times?

I'll try Yuxi, but as you may remember from last year, I'm not too good at making that work. (using Chrome if there's any hints avail) Also, it wouldn't show any Freqs. Indicated I had no AC capable of flying the route.

It wouldn't let me post the entire screen due to a space limit set by admin, but here's the jist of it.

• Market Research
• Competition
• Add Flights

PHX - DAL (876 miles)Select AircraftSet O/W Ticket PricesR/T FrequencyAircraftTypeSeatsMax PayloadHoursO/W Flight TimeTurn TimeR/T Block Time

Aircraft with insufficient hours: 2
Aircraft with incompatible schedules: 0

Disregard. The part you need didn't make it over. I'll try again.

• Market Research
• Competition
• Add Flights

PHX - DAL (876 miles)Select AircraftSet O/W Ticket PricesR/T FrequencyAircraftTypeSeatsMax PayloadHoursO/W Flight TimeTurn TimeR/T Block Time

Aircraft with insufficient hours: 2
Aircraft with incompatible schedules: 0

Same issue on DEN-DAL now. Still can't get the screen shot to work. Sorry.

SJC, SAN-DAL. Guess it's a DAL issue?

WAIT! Yuxi! Is the "Wright Amendment" in effect?

WAIT! Yuxi! Is the "Wright Amendment" in effect?

As far as I know. Maybe that's why?

Think so. I've "tested" it in several cities now. Anything outside "border" states to TX won't run. I like it!

Still have the "speed", or flit time issue. The "R/T" time looks OK, but the "O/W" time seems double. Just did SJC-MSP and got the same thing. Sorry I can't get a screen shot to work. It pastes OK, but when I hit "reply", it's not there.

Thx again Yuxi, to you and the team. 3.1 is an amazing achievement and huge improvement in reality.

Updating severity to: 1 - Low
Updating status to: Acknowledged, Waiting for Fix
Updating version to: None
Issue fixed in: None

Ah, right. The O/W flight time is mislabeled (or miscalculated, either/or) - I'll fix that later. It doesn't affect the R/T block time though, so the frequency calculations are correct.


I'll fix it tonight. and maybe we'll put in a relevant error message for the Wright Amendment


Thanks

Yeah I implemented the Wright Amendment.

Thanks again. And good one on the Wright Ammend UN1!

Im getting the same problem on DSM-BFI is blocked at 6:40 o/w 7:40rt when it should be WAY less.

Im getting the same problem on DSM-BFI is blocked at 6:40 o/w 7:40rt when it should be WAY less.

The O/W flight time is mislabeled (or miscalculated, either/or) - I'll fix that later. It doesn't affect the R/T block time though, so the frequency calculations are correct.

Updating status to: Fixed


This issue has been resolved. Thank you.

Yeah I implemented the Wright Amendment.

Wikipedia "Wright Amendment" Article

Quote: (from the above linked wikipedia article)

"Repeal compromise On June 15, 2006, it was announced that American, Southwest, DFW Airport and the cities of Dallas and Fort Worth had all agreed to seek full repeal of the Wright Amendment, with several conditions. Among them: The ban on nonstop flights outside the Wright zone would stay in place until 2014; through-ticketing to domestic and foreign airports (connecting flights to long-haul destinations) would be allowed immediately; Love Field's maximum gate capacity would be lowered from 32 to 20 gates; and Love would handle only domestic flights non-stop.

The proposed compromise was opposed by jetBlue Airways and other low-fare carriers, who argued that the gate reductions at Love would harm their ability to begin service there, and by area congressmen who opposed provisions of the deal that they believed would restrict competition in passenger service at other airports within an 80-mile (130 km) radius of DFW and Love, including Collin County Regional Airport in the nearby city of McKinney. The compromise was also opposed by Love Field Terminal Partners who own the old Legend Airlines terminal. They claimed that the announcement of the compromise prevented them from selling the six gate terminal to Pinnacle Airlines who had shown interest in purchasing or leasing the gates and have several law suits to prevent the compromise's implementation.

On July 25, 2006, a leaked memorandum from an employee of the United States Department of Justice Antitrust Division raised concerns about airline competition in North Texas and urged legislators to force a renegotiation of the deal. It also stated that the removal of gates and a cap of 20 gates for the airport would violate federal anti-trust legislation. This capping of gates would affect the other airlines that might be attracted to getting gates there at Dallas Love Field airport.

Sen. Kay Bailey Hutchison responded to the memorandum by stating "They [Justice] are not taking a position at all on the legislation... That memo did not go through the channels. And it probably was one person's view, but it's not the Justice Department's."

Judiciary Committee Chairman James Sensenbrenner also had some complaints about the anti-trust issues that he thought would arise from the proposed legislation.

After extensive negotiations with the House and Senate Judiciary Committees, the compromise bill passed both Houses of Congress on Friday, September 29, just before the 109th Congress adjourned for the November elections. Hutchison led the effort to pass the bill in the Senate while Rep. Kay Granger led a bipartisan Texas House coalition to see the bill through to a successful conclusion in the House. President George W. Bush signed the bill into law on October 13, 2006. Southwest and American airlines then required approval from the Federal Aviation Administration to begin one-stop flights from Love Field to destinations outside the Wright limits.

Even though direct connections are restricted until 2014, Southwest Airlines announced on October 17, 2006 that it would begin indirect connecting service between Love Field and 25 destinations outside the Wright zone on October 19, 2006. American Airlines also made indirect connecting travel between Love Field and locations outside the Wright zone available by October 18, 2006."

So my question is, will the admins adjust the DAL restrictions to be in line with current events as quoted in the wiki article ?

According to the article, Prior to the Wright Amendment ending the states (in addition to Texas) that airlines could fly to:

Louisiana, Arkansas, Oklahoma, New Mexico, Alabama, Kansas, Mississippi, and Missouri

Also, when you implement one stop flights will this allow one stop flights to/from DAL as per the new provisions of the October 13, 2006 law signed by George W. Bush allowing:

1) through-ticketing to domestic and foreign airports (connecting flights to long-haul destinations) would be allowed immediately
2) direct service to destinations outside the Wright zone after 2014 (non-stop flights limited to domestic USA only)
3) one-stop flights to destinations outside the Wright zone after 2014 via airports inside the Wright Zone

1) "Stopovers" refer to fuel stops, not "1-stop flights". You can set up multiple flights and pretend they are "through ticketing" - how flights are ticketed is not simulated in AE anyway.
2) Discussion about the Wright Amendment belongs in feature requests, not the bug tracker.

As this bug report is now off topic, I will close it.