Compare Boeing 737-200 add-ons for FSX, Prepar3D and FS2004, including panels, liveries, sounds, compatibility and the best package for each need.
In our freeware library, Boeing 737-200 add-ons are concentrated on FSX and FS2004, with one package also intended for Prepar3D. Choices include complete aircraft with panels, JT8D sounds and flight dynamics, plus livery-heavy YeoDesigns and regional packs. These files do not install directly in Microsoft Flight Simulator 2020/2024 or X-Plane.
Boeing 737-200 add-ons by simulator
Six complete or near-complete Boeing 737-200 packages cover FSX, FS2004 and, with caveats, Prepar3D.
| Package | Platform stated | Main features | Best suited to |
|---|---|---|---|
| Complete FSX package with a 2D cockpit | FSX and Prepar3D | Updated flight dynamics, panel, sounds and a 2D cockpit | An all-in-one starting point, especially for pilots who prefer traditional pop-up panels |
| Multi-livery V1.1 package with JT8D sounds | FSX | Several airline liveries, a PSPanels cockpit and JT8D engine audio | Classic airline operations and a broader livery selection |
| Animation-focused YeoDesigns V2 release | FSX | Canadian and regional liveries, lighting, stairs, opening doors and thrust reversers | Exterior detail, screenshots and ramp operations |
| Original YeoDesigns 737-200 Pack | FSX | Basic virtual cockpit, effects, an updated FSX model, and United and Air New Zealand liveries | Pilots who need a virtual cockpit rather than a mainly 2D-panel experience |
| Indonesian Boeing 737-200 Pack | FSX | Multiple Indonesian airline liveries, custom panel and sounds, plus GPS options | Regional Indonesian routes and pilots wanting convenient GPS navigation |
| AirCal aircraft for FS2004 | FS2004 | AirCal-themed 737-200 aircraft and livery | Users retaining a dedicated FS2004 installation |
Check that a download is a complete aircraft rather than a repaint before installing it. A complete legacy package normally contains aircraft.cfg together with model, panel, sound and texture folders; a repaint may contain only a texture folder and configuration instructions.
Which Boeing 737-200 package should I choose?
Choose by simulator and cockpit type first, then compare liveries, sounds and exterior animations.
- For a complete general-purpose aircraft: start with the FSX package containing its own panel, sounds and updated flight dynamics.
- For airline variety and JT8D audio: the V1.1 multi-livery package is the stronger fit.
- For animated doors, stairs and reversers: choose YeoDesigns V2.
- For virtual-cockpit flying: the original YeoDesigns pack explicitly includes a basic virtual cockpit. Do not assume a package described around a 2D panel has a detailed VC.
- For regional routes: use the Indonesian pack or the AirCal FS2004 aircraft according to the simulator and airline required.
These are legacy freeware aircraft, not modern study-level simulations. Panel complexity varies, and attractive exterior modelling does not guarantee deeply simulated electrical, pneumatic or navigation systems.
Will an FSX 737-200 work in MSFS 2020 or 2024?
No, an FSX Boeing 737-200 cannot be installed directly into Microsoft Flight Simulator 2020 or 2024, and it is not compatible with X-Plane.
- Prepar3D: use only a package that explicitly lists Prepar3D, then check its documentation against your particular release. Older gauges and effects may fail even when the exterior model loads.
- Microsoft Flight Simulator 2020/2024: copying an FSX aircraft folder into the Community folder does not convert its model, gauges or flight model.
- X-Plane: its aircraft format and systems architecture are different, so FSX files cannot be reused as an installable aircraft.
- Xbox and PlayStation: downloadable FSX folders are PC add-ons and cannot be manually installed on console editions.
What cockpit and navigation features should I expect?
Expect an analogue 737 flight deck and conventional radio navigation rather than the modern 737NG-style FMC, LNAV and VNAV workflow.
The real 737-200 predates the glass-cockpit layout familiar from later variants, although individual aircraft received avionics upgrades. In these add-ons, a listed GPS option may be a convenient pop-up instrument rather than a fully integrated or period-authentic flight-management system.
Before choosing a package, check whether it provides a 2D panel, virtual cockpit or both. Also verify that the autopilot, VOR/ILS equipment and supplied gauges match the way you intend to fly; these details matter more than the number of liveries.
How do I install an FSX or FS2004 737-200?
Install the aircraft into the folder used by its stated simulator and follow the included readme for any separate gauges, effects or sounds.
- Confirm the simulator. Do not install an FS2004 package into FSX merely because both use an
aircraft.cfgfile. - Extract the archive first. Do not run the aircraft from inside the ZIP file.
- Find the actual aircraft folder. It should contain
aircraft.cfgalongside the model, panel, sound and texture folders. - Copy it to the correct location. FSX normally uses
SimObjects\Airplanes; FS2004 uses itsAircraftdirectory. Copy separate Effects or Gauges files only when the documentation instructs you to do so. - Restart the simulator. Look under Boeing, the package developer or the airline name, since the menu entry depends on fields inside
aircraft.cfg.
Why does the aircraft not appear or load correctly?
A double-nested aircraft folder is the most common cause of a missing 737-200. The simulator must reach aircraft.cfg directly inside the individual aircraft folder, not through an extra wrapper directory created during extraction.
- Blank panel: recheck the readme for supplied gauges and confirm that they support the simulator being used.
- No engine sounds: inspect whether the sound folder is complete or aliases another aircraft that is not installed.
- Invisible or badly rendered model: the model is usually being loaded by an incompatible simulator generation.
- Only some liveries are missing: the repaint entries in
aircraft.cfgmay be absent, incorrectly numbered or pointing to the wrong texture-folder name.