Find freeware Lancair 320, 360 and LNC2 aircraft add-ons, check simulator compatibility, and avoid confusing the Legacy or Lancair IV-P.
Freeware Lancair aircraft are available in our downloads library, especially for FSX and Prepar3D. Start with the complete RSDG Lancair package or the red, black and white FSX package. Search both “Lancair 320/360” and “LNC2”, but check the documentation because LNC2 is usually a type designator, not the product name.
Which Lancair aircraft downloads should I try?
The two closest matches in our library are complete FSX-era aircraft packages rather than texture-only repaints.
- RSDG Lancair: A complete aircraft with an enhanced flight model, textures and air brakes. Its listing covers FSX and Prepar3D, making it the best starting point for either simulator.
- Red, black and white Lancair: An FSX package containing updated flight dynamics, configuration files and reflective textures. It provides an alternative installation and colour scheme.
The download title may simply say “Lancair”, so read the included documentation before treating it as an exact 320 or 360 simulation. If the precise variant matters for performance figures, online flying or aircraft identification, a generic Lancair label is not enough.
Do not confuse these with the Lancair IV-P Gold Edition for FSX and Prepar3D. The IV-P belongs to the same manufacturer’s family but is not a Lancair 320 or 360 substitute.
Is LNC2 the same as a Lancair 320 or 360?
LNC2 is an ICAO aircraft type designator, while Lancair 320 and Lancair 360 are specific model names. Add-on authors may put LNC2 in configuration data without using it in the download title.
| Label | What it tells you | What to check |
|---|---|---|
| Lancair 320 | Variant normally associated with the Lycoming O-320 installation | Readme, engine data and stated performance |
| Lancair 360 | Variant normally associated with the more powerful Lycoming O-360 installation | Readme, engine data and stated performance |
| LNC2 | Type code used in flight planning, ATC or aircraft configuration data | It does not by itself distinguish a 320 from a 360 |
Which flight simulators can use these Lancair add-ons?
These legacy packages should be installed only in simulators for which they are explicitly listed.
| Simulator | Compatibility |
|---|---|
| FSX | The primary platform for both packages above |
| Prepar3D | Use a package that specifically lists Prepar3D; gauge behaviour can vary between generations |
| FS2004 | Requires an FS2004-specific build rather than the FSX package |
| MSFS 2020 or 2024 | FSX aircraft cannot be installed directly; a native MSFS conversion or separate model is required |
| X-Plane | Requires a native X-Plane aircraft package |
For another platform, search our freeware aircraft and add-ons library and verify the simulator tag before downloading. A matching aircraft name does not make files portable between FSX, MSFS and X-Plane.
How can I confirm the package is really a 320 or 360?
- Read the included documentation. Look for an explicit model designation rather than relying on the archive or folder name.
- Inspect the FSX configuration. Fields such as
title,ui_type,descriptionandatc_modelmay identify the aircraft. Anatc_modelvalue of LNC2 still does not prove whether it represents a 320 or 360. - Check the simulated engine. The documented engine and performance should agree with the claimed variant; generic or modified flight dynamics may not.
- Confirm it is a complete aircraft. A download containing only a texture folder and configuration entries is a repaint and needs its stated base model.
Why does the Lancair not appear after installation?
The usual causes are an extra nested folder, a missing base aircraft or a package built for another simulator. In FSX and Prepar3D, the folder containing aircraft.cfg must be placed directly in an active aircraft search location; it should not be buried inside a second identically named folder.
If the aircraft appears but its panel is blank, the model is installed and the problem is more likely an incompatible or missing legacy gauge. Recheck the package instructions rather than repeatedly moving the aircraft folder.