There are a few uses for Sbus on a fixed wing aircraft.
First up, it is usually used to add more channels to a receiver. Lets say you need 4 more channels, you can either add Sbus servos and tell them what channel to use, or you can use an Sbus decoder and tell it what channels to output and plug normal PWM servos into the decoder.
Another option is to use Sbus in a redundant receiver setup, this way if the main receiver is having reception issues for any reason, it can get the needed data from a secondary receiver. With just 1 servo extension running between the 2 receivers, the second receiver can be located a good distance away where it can get cleaner reception. (great for planes with a lot of metal, wires or carbon where the main receiver needs to be placed.
And a less common setup is when feeding a gyro or some sort of flight controller. Rather than passing a bunch of wires between a receiver and the controller, you can have a single connection pass all of the channels.
For added fun lets talk a bit about Smart Port (Sport, S.Port, etc) Many people get Sbus and S.port confused. Sbus carries the channels data, and S.port carries the telemetry data.
With the newest ACCESS receivers you have the option of setting up F.Port, this combines both the S.Port and Sbus into a single data stream. Again this cleans up wiring in the aircraft. Frsky's new servos support F.port, so when you plug one into a receiver you also get lots of nice sensor data from that servo.
If you do not want to use these things, you do not need to. You can build planes like you always have, no problems, this is what I typically do.
