2025-04-16T01:01:57.711Z - Using Microsoft Flight Simulator X
2025-04-16T01:01:57.711Z - Flying Boeing 737-900ER Delta Airlines FREEWARE_(C)_TDS_16AUG2013_739_CFM56-7BE--P2W2_+A3800_+D00_+B1
2025-04-16T01:01:57.712Z - Now boarding
2025-04-16T01:01:57.713Z - COM1: 121.700, COM2: 127.800, NAV1: 110.75, NAV2: 110.10, Transponder: 2572
2025-04-16T01:02:47.992Z - Paused
2025-04-16T01:02:48.994Z - Unpaused
2025-04-16T01:03:12.093Z - Engine 1 On
2025-04-16T01:03:38.251Z - Engine 2 On
2025-04-16T01:03:43.272Z - Pushing back with 10000 LBS of fuel
2025-04-16T01:03:47.297Z - Taxiing out
2025-04-16T01:04:34.305Z - Comment: BETA TEST FLIGHT: Intentionally closing FSX mid-flight to test BETA reconnect following CTD situation.
2025-04-16T01:04:44.697Z - Flaps set to 12%
2025-04-16T01:04:47.724Z - Flaps set to 25%
2025-04-16T01:05:42.318Z - Taking off
2025-04-16T01:05:57.509Z - Climbing at 177 kts, 5 degrees pitch, 0 degrees bank
2025-04-16T01:06:01.553Z - Flaps set to 12%
2025-04-16T01:06:03.589Z - Gear lever raised
2025-04-16T01:06:06.620Z - Flaps set to 0%
2025-04-16T01:07:54.540Z - NAV1 active frequency set to 110.10
2025-04-16T01:13:03.169Z - Cruising at 15000 FT
2025-04-16T01:20:17.140Z - Paused
2025-04-16T01:20:18.140Z - Unpaused
2025-04-16T01:20:53.832Z - Comment: TEST POINT HERE! Will be shutting down FSX right after this message comment is saved to log.
2025-04-16T01:28:29.042Z - Slew mode entered
2025-04-16T01:29:00.173Z - Slew mode left
2025-04-16T01:36:29.869Z - Comment: RESUMPTION POINT HERE! SC3 did not recognize exact spot of crash. Had saved the flight before closing FSX, yet SC3 indicated I was 26nm too far forward. Had to slew backwards to correct position then SC3 automaticallly resumed logging, however it indicated "slew mode active" which would violate regular PIREP submission rules. At least within FSX, I wasn't able to slew position while I was paused.. SC3 auto-resumes once at 5nm from last detected spot, so only way to use this feature without a slew indication would be to REFLY it from the start, do a time warp/compression until you're about 10nm from the SC3 spot, then go back to regular time before SC3 resumes the logging. SC3 provides a pop-up window indicating distance in real-time so you can resume normal time shortly before SC3 would resume tracking.
2025-04-16T01:52:29.243Z - Descending with 52 nm to go
2025-04-16T01:54:39.762Z - Approach started at 12277 FT AGL with 42 nm to go
2025-04-16T01:55:06.909Z - Flaps set to 12%
2025-04-16T02:01:43.244Z - Flaps set to 25%
2025-04-16T02:02:09.569Z - Flaps set to 37%
2025-04-16T02:03:24.477Z - Flaps set to 50%
2025-04-16T02:03:38.593Z - Gear lever lowered
2025-04-16T02:03:41.626Z - Flaps set to 62%
2025-04-16T02:03:59.812Z - Flaps set to 75%
2025-04-16T02:04:23.136Z - Flaps set to 87%
2025-04-16T02:04:44.341Z - Flaps set to 100%
2025-04-16T02:05:23.785Z - On final at 3319 FT with 4 nm to go at 149 kts, -4 degrees pitch, 0 degrees bank
2025-04-16T02:06:53.288Z - Touched down at -50 fpm, 1.0g, 134 kts, -1 degrees pitch, 0 degrees bank
2025-04-16T02:07:21.490Z - Taxiing to gate, landed in 3527 FT
2025-04-16T02:08:09.976Z - Flaps set to 87%
2025-04-16T02:08:13.008Z - Flaps set to 75%
2025-04-16T02:08:17.019Z - Flaps set to 62%
2025-04-16T02:08:20.046Z - Flaps set to 50%
2025-04-16T02:08:24.070Z - Flaps set to 37%
2025-04-16T02:08:28.096Z - Flaps set to 25%
2025-04-16T02:08:31.106Z - Flaps set to 12%
2025-04-16T02:08:33.121Z - Flaps set to 0%
2025-04-16T02:10:39.181Z - Engine 1 Off
2025-04-16T02:10:39.181Z - Engine 2 Off
2025-04-16T02:13:26.847Z - Comment: PIREP submitted so it can be shared with SC3. Issues to consider - manual resume instead of automatic. If slewing or time accelerating to crash point it gets picked up in log. Item 2: can SC3 indicate a log entry for when a connection loss was detected and when it was reestablished?