Flight CRGMGP130
|
|
Additional Log Information:
2025-07-13T00:49:22.774Z - Using Microsoft Flight Simulator X
2025-07-13T00:49:22.774Z - Flying Project Opensky - Boeing 747-8F FEDEX
2025-07-13T00:49:22.775Z - Now boarding
2025-07-13T00:49:22.775Z - COM1: 128.300, COM2: 127.900, NAV1: 109.70, NAV2: 110.60, Transponder: 1200
2025-07-13T00:50:06.093Z - Pushing back with 354023 LBS of fuel
2025-07-13T00:50:25.218Z - Engine 1 On
2025-07-13T00:50:49.390Z - Engine 2 On
2025-07-13T00:51:14.554Z - Engine 3 On
2025-07-13T00:51:21.789Z - Taxiing out
2025-07-13T00:51:39.883Z - Engine 4 On
2025-07-13T00:51:50.970Z - Flaps set to 16%
2025-07-13T00:51:55.999Z - Flaps set to 33%
2025-07-13T00:55:41.971Z - Taking off
2025-07-13T00:56:15.364Z - Climbing at 178 kts, 10 degrees pitch, 0 degrees bank
2025-07-13T00:56:18.384Z - Flaps set to 16%
2025-07-13T00:56:18.384Z - Gear lever raised
2025-07-13T00:56:30.472Z - Flaps set to 0%
2025-07-13T00:56:40.554Z - Pitch exceeded 20 degrees nose up
2025-07-13T01:10:32.548Z - Cruising at 34000 ft
2025-07-13T01:18:03.183Z - NAV1 active frequency set to 110.30
2025-07-13T11:07:00.505Z - Paused
2025-07-13T13:42:19.122Z - Unpaused
2025-07-13T13:53:37.587Z - Flaps set to 16%
2025-07-13T13:59:12.297Z - Descending with 23 nm to go
2025-07-13T14:00:22.835Z - Flaps set to 33%
2025-07-13T14:01:06.142Z - Flaps set to 50%
2025-07-13T14:02:28.883Z - Flaps set to 66%
2025-07-13T14:07:05.153Z - Flaps set to 83%
2025-07-13T14:10:51.038Z - Approach started at 8085 ft AGL with 32 nm to go
2025-07-13T14:13:16.280Z - Flaps set to 100%
2025-07-13T14:15:56.725Z - Comment: Flight tracking disconnected
2025-07-13T16:17:34.650Z - Comment: Flight tracking reconnected
2025-07-13T16:17:35.584Z - Flaps set to 50%
2025-07-13T16:17:48.738Z - Flaps set to 66%
2025-07-13T16:18:03.918Z - Flaps set to 83%
2025-07-13T16:18:32.280Z - Flaps set to 100%
2025-07-13T16:19:08.249Z - Comment: Flight tracking disconnected
2025-07-13T16:22:27.430Z - Comment: Flight tracking reconnected
2025-07-13T16:23:07.107Z - Comment: Suspected bad scenery file caused 2 CTDs. Third attempt to land after removing add-on scenery for WMSA airport.
2025-07-13T16:31:31.364Z - Gear lever lowered
2025-07-13T16:31:32.367Z - Touched down at -971 fpm, 1.0g, 152 kts, 4 degrees pitch, 0 degrees bank
2025-07-13T16:32:15.791Z - Taxiing to gate, landed in 5538 FT
2025-07-13T16:32:33.968Z - Flaps set to 83%
2025-07-13T16:32:38.002Z - Flaps set to 33%
2025-07-13T16:32:40.013Z - Flaps set to 16%
2025-07-13T16:32:47.067Z - Flaps set to 16%
2025-07-13T16:32:49.084Z - Flaps set to 0%
2025-07-13T16:36:52.953Z - Engine 1 Off
2025-07-13T16:36:52.953Z - Engine 2 Off
2025-07-13T16:36:52.953Z - Engine 3 Off
2025-07-13T16:36:52.953Z - Engine 4 Off
2025-07-13T16:46:40.868Z - Comment: SUBMITTING PIREP FOR SC3 ERROR REVIEW. After the second CTD, add-on scenery was removed allowing a normal landing on third attempt. SC3 indicated that it reconnected for the third attempt but did not register any actions (flaps changes, gear down) until after I landed. Actual sim landing was typical (roughly -150 fpm) but entries for gear and landing didn't register until moments after landing. Almost like SC3 was hung up along the approach and needed the landing to resync or reengage the connection. Pulling log files from SC3 so they can be examined if necessary. The CTDs occurred at the same point, about 13nm from the airfield and after already capturing the ILS feather for descent.
2025-07-13T00:49:22.774Z - Flying Project Opensky - Boeing 747-8F FEDEX
2025-07-13T00:49:22.775Z - Now boarding
2025-07-13T00:49:22.775Z - COM1: 128.300, COM2: 127.900, NAV1: 109.70, NAV2: 110.60, Transponder: 1200
2025-07-13T00:50:06.093Z - Pushing back with 354023 LBS of fuel
2025-07-13T00:50:25.218Z - Engine 1 On
2025-07-13T00:50:49.390Z - Engine 2 On
2025-07-13T00:51:14.554Z - Engine 3 On
2025-07-13T00:51:21.789Z - Taxiing out
2025-07-13T00:51:39.883Z - Engine 4 On
2025-07-13T00:51:50.970Z - Flaps set to 16%
2025-07-13T00:51:55.999Z - Flaps set to 33%
2025-07-13T00:55:41.971Z - Taking off
2025-07-13T00:56:15.364Z - Climbing at 178 kts, 10 degrees pitch, 0 degrees bank
2025-07-13T00:56:18.384Z - Flaps set to 16%
2025-07-13T00:56:18.384Z - Gear lever raised
2025-07-13T00:56:30.472Z - Flaps set to 0%
2025-07-13T00:56:40.554Z - Pitch exceeded 20 degrees nose up
2025-07-13T01:10:32.548Z - Cruising at 34000 ft
2025-07-13T01:18:03.183Z - NAV1 active frequency set to 110.30
2025-07-13T11:07:00.505Z - Paused
2025-07-13T13:42:19.122Z - Unpaused
2025-07-13T13:53:37.587Z - Flaps set to 16%
2025-07-13T13:59:12.297Z - Descending with 23 nm to go
2025-07-13T14:00:22.835Z - Flaps set to 33%
2025-07-13T14:01:06.142Z - Flaps set to 50%
2025-07-13T14:02:28.883Z - Flaps set to 66%
2025-07-13T14:07:05.153Z - Flaps set to 83%
2025-07-13T14:10:51.038Z - Approach started at 8085 ft AGL with 32 nm to go
2025-07-13T14:13:16.280Z - Flaps set to 100%
2025-07-13T14:15:56.725Z - Comment: Flight tracking disconnected
2025-07-13T16:17:34.650Z - Comment: Flight tracking reconnected
2025-07-13T16:17:35.584Z - Flaps set to 50%
2025-07-13T16:17:48.738Z - Flaps set to 66%
2025-07-13T16:18:03.918Z - Flaps set to 83%
2025-07-13T16:18:32.280Z - Flaps set to 100%
2025-07-13T16:19:08.249Z - Comment: Flight tracking disconnected
2025-07-13T16:22:27.430Z - Comment: Flight tracking reconnected
2025-07-13T16:23:07.107Z - Comment: Suspected bad scenery file caused 2 CTDs. Third attempt to land after removing add-on scenery for WMSA airport.
2025-07-13T16:31:31.364Z - Gear lever lowered
2025-07-13T16:31:32.367Z - Touched down at -971 fpm, 1.0g, 152 kts, 4 degrees pitch, 0 degrees bank
2025-07-13T16:32:15.791Z - Taxiing to gate, landed in 5538 FT
2025-07-13T16:32:33.968Z - Flaps set to 83%
2025-07-13T16:32:38.002Z - Flaps set to 33%
2025-07-13T16:32:40.013Z - Flaps set to 16%
2025-07-13T16:32:47.067Z - Flaps set to 16%
2025-07-13T16:32:49.084Z - Flaps set to 0%
2025-07-13T16:36:52.953Z - Engine 1 Off
2025-07-13T16:36:52.953Z - Engine 2 Off
2025-07-13T16:36:52.953Z - Engine 3 Off
2025-07-13T16:36:52.953Z - Engine 4 Off
2025-07-13T16:46:40.868Z - Comment: SUBMITTING PIREP FOR SC3 ERROR REVIEW. After the second CTD, add-on scenery was removed allowing a normal landing on third attempt. SC3 indicated that it reconnected for the third attempt but did not register any actions (flaps changes, gear down) until after I landed. Actual sim landing was typical (roughly -150 fpm) but entries for gear and landing didn't register until moments after landing. Almost like SC3 was hung up along the approach and needed the landing to resync or reengage the connection. Pulling log files from SC3 so they can be examined if necessary. The CTDs occurred at the same point, about 13nm from the airfield and after already capturing the ILS feather for descent.
Comments
Commenter | Comment |
---|---|
Steve Kightlinger | 2025-07-13T14:15:56.725Z - Comment: Flight tracking disconnectedn2025-07-13T16:17:34.650Z - Comment: Flight tracking reconnectedn2025-07-13T16:19:08.249Z - Comment: Flight tracking disconnectedn2025-07-13T16:22:27.430Z - Comment: Flight tracking reconnectedn2025-07-13T16:23:07.107Z - Comment: Suspected bad scenery file caused 2 CTDs. Third attempt to land after removing add-on scenery for WMSA airport.n2025-07-13T16:46:40.868Z - Comment: SUBMITTING PIREP FOR SC3 ERROR REVIEW. After the second CTD, add-on scenery was removed allowing a normal landing on third attempt. SC3 indicated that it reconnected for the third attempt but did not register any actions (flaps changes, gear down) until after I landed. Actual sim landing was typical (roughly -150 fpm) but entries for gear and landing didn't register until moments after landing. Almost like SC3 was hung up along the approach and needed the landing to resync or reengage the connection. Pulling log files from SC3 so they can be examined if necessary. The CTDs occurred at the same point, about 13nm from the airfield and after already capturing the ILS feather for descent. |
Steve Kightlinger | exceeded -800 fpm. |
Steve Kightlinger | Interesting note - Landing shows I was at 1.0g ... if I had truly landed in excess of 900 fpm shouldn't the g-forces have been much higher?? |