Flight #2054652

Flight summary

Callsign: N479CX
From / To: LPPT Lisbon LEMD Barajas
Pilot: Clorix
Aircraft: Beechcraft Super King Air 350 (B350)
Planned Cruise: FL310
Landing rate: -94 ft/min 0.95 g
Flight time: 01:09
Distance: 335 nm
Fuel burnt: 328 KGS
ZFW: 5.0 t
Payload: 436 KGS
Max. Altitude: 32,141 ft
Max. Speed: 318 kts
Average Speed: 248 kts
Planned Route: LPPT OGERO ROLDO RUKER LEMD
Tags: Microsoft Flight Simulator MFS MSFS FS2020 MFS2020 MSFS2020 Microsoft Flight Simulator 2020 2020 beechcraft beech king air 350 350 b350 analog black square LPPT Lisbon LEMD Barajas Madrid ILS approach cat i approach cat i cat i ils cat i ils approach cat 1 category 1 category i greased it butter greaser amazing landing landing daily challenge joinfs multiplayer FsHub multiplayer scenic scenery sightseeing
Remarks: This was a mostly uneventful flight. I say "mostly" because there WAS an issue that I inadvertently caused without realizing what happened until a bit later. During cruise, I was taking screenshots when my aircraft abruptly began climbing. At first I thought this was just some turbulence as I had just recently gone through a couple turbulent spots. But this time the aircraft never settled back down. I hopped back into the cockpit and noticed that the flight director was commanding a pitch of about +10 degrees. It has never done this before. Just before it had climbed 1000 feet above my cruise altitude (and pressurization setting!), I took manual control and began descending back to FL310. I checked the circuit breakers thinking maybe one had popped, but that wasn't the case. I tried re-engaging the autopilot, but it once again began to climb quickly. I took control again and set a VS of 0 FPM. That caused the flight director to respond how I thought it should again. So I set a gentle descent back down to FL310 again, and it captured the selected altitude just as it should, and there were no further issues. After I regained my composure and control of the aircraft, I went back to taking screenshots. It was at THIS point I realized what happened. While taking screenshots, I had set my camera view outside the aircraft. The way I do this is either by using the external camera (where it keeps the plane centered and revolves around the plane), or the drone camera (which can be controlled to a much more precise degree). In the drone camera, my controls control just the drone camera, not the plane. But in the external camera mode, the plane CAN be controlled. So what happened was I didn't realize I was in the external camera mode and went to reset the pan and tilt of the camera - except this isn't possible in external camera mode. The button I use to do this in drone camera mode is the same button I have set to engage TO/GA mode. And when I pressed that button while in external camera mode, my aircraft, at FL310, started to do exactly what I told it to do. Lesson learned! And it made for a more exciting flight!
Take-off Landing
Airport LPPT Lisbon LEMD Barajas
Country PT Portugal ES Spain
Time 26OCT22 0145Z 26OCT22 0255Z
Local 26OCT22 0245 26OCT22 0455
Fuel 786 KGS 458 KGS
GW 5.7 t 5.4 t
Heading 205° 321°
Speed TAS 118 kts 89 kts
Pitch
Bank
Winds 220° @ 8 kts 000° @ 5 kts
Simulator: Microsoft Flight Simulator 2020 Microsoft Flight Simulator 2020
Flags: Daily Challenge Live Screenshots

Flight gallery View all (12)

There are 2 more screenshots for this flight report, would you like to view the full flight gallery?

Flight path GeoJSON

Loading map data...

Flight chart

Loading chart data...