Imported schedule, delete leg, lose times...

JustinB

Active member
Joined
Feb 5, 2003
Messages
37
This was originally posted in APDL import support:

Good morning,

Here is a schedule that I just imported. I am using the latest versions of all the software.

D3A11A : 01OCT ONLY ON SUN BSE REPT: 1200L Operates: Oct 1 Only
Base/Equip: DEN/319 FO01
DY DH C FLTNO DPS-ARS DEPL ARRL BLKT GRNT TBLK TDHD TCRD TPAY TDUTY LAYOVER
SU NTR DEN-DEN 1355 1356 0000 0059
SU 575 DEN-SLC 1455 1615 0120 0040
SU 129 SLC-DEN 1655 1815 0120 0240 0240 0630
D-END: 1830L T.A.F.B.: 0630
Total: 0240 0000 0000 0240 0630

In APDL on the PPC, you see the three lines, NTR, Flight 575, and 129, the times are correct on each line. I choose to delete the first leg, NTR. Now the two legs that are left are 575 and 129, however, both of the scheduled times are the same, 1655 departure and 1815 arrival. The times 1455 and 1615 are lost for flight 575.

Can anyone else duplicate this? My PPC time is set to local when I import, I switch it to zulu after the import.

{Imported to PPC with the Frontier filter}
Thanks,
Justin
 

JustinB

Active member
Joined
Feb 5, 2003
Messages
37
Update:

Okay..I imported the schedule again, with the logbook set to local. All times imported matched correctly.

I switched the logbook to zulu time, still, all times matched correctly.

Then I deleted the NTR leg, now the times are as follows:

DEN-SLC 1455-1619 (Mountain time or imported time)
(DEN-SLC 2055-2219 are what the times should have been)

SLC-DEN 2255-0010 (correct zulu time)

Weird.

Justin
 
Last edited:

JustinB

Active member
Joined
Feb 5, 2003
Messages
37
Must be Oct 1 or that pairing

I just imported another pairing that is very similar:

D3A32B : 02OCT ONLY ON MON BSE REPT: 1200L Operates: Oct 2 Only
Base/Equip: DEN/319 FO01
DY DH C FLTNO DPS-ARS DEPL ARRL BLKT GRNT TBLK TDHD TCRD TPAY TDUTY LAYOVER
MO NTR DEN-DEN 1710 1711 0000 0059
MO 405 DEN-LAX 1810 1935 0225 0040
MO 416 LAX-DEN 2015 2325 0210 0435 0435 1140
D-END: 2340L T.A.F.B.: 1140
Total: 0435 0000 0000 0435 1140

I deleted the NTR leg and it worked fine. (Not really -- see next post)

Go figure.

Justin
 
Last edited:

JustinB

Active member
Joined
Feb 5, 2003
Messages
37
Okay...I said in the last post that it worked fine, but I lied. It is doing someting a little different now. Maybe they threw in a bad Pentium in my 8125. :)

Here is the schedule I imported:
D3A49B : 03OCT ONLY ON TUE BSE REPT: 1200L Operates: Oct 3 Only
Base/Equip: DEN/319 FO01
DY DH C FLTNO DPS-ARS DEPL ARRL BLKT GRNT TBLK TDHD TCRD TPAY TDUTY LAYOVER
TU NTR DEN-DEN 1710 1711 0000 0059
TU 405 DEN-LAX 1810 1935 0225 0040
TU 416 LAX-DEN 2015 2325 0210 0435 0435 1140
D-END: 2340L T.A.F.B.: 1140
Total: 0435 0000 0000 0435 1140

Same thing, but different.

Import, it is all accurate. Delete the NTR leg, it is all accurate except for the LAX in time, it changes from 1935 to 2035. The same thing happened on yesterdays pairing, I just didn't catch it until I was entering the times in the A/C.

I have LAX set to UTC-8 and apply daylight savings time.

What in the heck is going on?

Justin
 

Paul Auman

APDL Developer
Staff member
Joined
May 30, 2005
Messages
176
Location
Dunedin, FL
Justin,

The NTR portion of the schedule is a marker your airline uses to identify a "No Trip Rig".

From your PPC make sure on the "Timezone Settings" page you have "Import Schedule In ?" set to "Local". Leave this set to local.

On your main logpage. Set the "Timezone Selector" to "Logbook" and reimport the trip. The times should import correctly.

Fly Safe!

Paul Auman
 
Top