Instead of creating a new thread for each issue I suspect with the data, I'm going to keep all the posts under one thread.

Please keep in mind that I'm going to post some of the issues which may not be actual bugs but patterns that might signal underlying issues.

Issue: Some ASDI Flight Plans entries indicate 1970-01-01 00:00:00 (unix time 0) for some timestamps. Is this indicative of "Unavailable Data"?

Solution: Awaiting response from admininstrators

Filename: asdiflightplan.csv

Example File: \InitialTrainingSet_rev1\2012_11_15\ASDI\asdiflightplan.csv

Example Line: 311083

Example Line Content: 

1239422,2012-11-16 13:09:52,280771891,KSDF,KGEG,UPS982,KSDF./.SEA089036..ZOOMR.ZOOMR1.KGEG,2012-11-16 08:23:00,2012-11-16 09:12:00,1970-01-01 00:00:00,2012-11-16 13:28:00

SOLVED

Issue: A very small number (About 35) of Flight History Events have a timezone of -07. Is there an issue with the timezone adjustment script?

Solution: No timezones were modified in this file on Kaggle's side, so this simply reflects daylight savings time.

Filename: flighthistoryevents.csv

Example File: \InitialTrainingSet_rev1\2012_11_12\FlightHistory\flighthistoryevents.csv

Example Line: 53176

Example Line Content: 

279521153,2012-11-02 10:24:45.552-07,RecordCreated,

279521153,2012-11-02 10:24:45.552-07,RecordCreated,

All those dates are under a different time saving regime, it's still PST. It's another question whether the dates are correct.

279521153,2012-11-02 10:24:45.552-07,RecordCreated,

I'm not an administrator but I suspect this issue and the one before it are due to Daylight savings time in the US.  The date in the record, 2012-11-02, is in the period the US would have been observing Daylight savings time.  If all the records with issues were created before 2012-11-04, then I think the times reflect Daylight savings time.

Yup, that's what I intended to convey too. I certainly wasn't at my best phrasing that sentence.