# "default" profiles: base type unexpectedly used in place of ICAO type designator
**URL:** https://forum.navigraph.com/t/default-profiles-base-type-unexpectedly-used-in-place-of-icao-type-designator/24332
**Category:** Dispatch
**Created:** [September 19, 2026, 9:01pm UTC](https://forum.navigraph.com/t/default-profiles-base-type-unexpectedly-used-in-place-of-icao-type-designator/24332 "2026-09-19T21:01:45Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Rodeo314](https://forum.navigraph.com/u/Rodeo314)
#### Post date: [September 19, 2026, 9:01pm UTC](https://forum.navigraph.com/t/default-profiles-base-type-unexpectedly-used-in-place-of-icao-type-designator/24332/1 "2026-09-19T21:01:45Z")
Planning through Simbrief with e.g. the Lineage 1000 (official ICAO type designator E190, Simbrief internal base type E19L, to differentiate from the airliner E190), the flight plan text uses the fictitious base type E19L instead of the real-world designator:
LIDO
```txt
N191SB 19SEP2026 LSGG-CYVR E19L N191SB RELEASE 2037 19SEP26
```
BER
```txt
N191SB/N191SB N191SB/E19L SELCAL/ ROUTE: DEFRTE
```
WZZ
```txt
C/S*: N191SB N191SB/+0.0 E19L | LSGG/GVA 1915 1915 +02.00
```
This does not happen with all profiles, e.g. the iniBuilds Atlas (code: A400, base: A343) and Beluga XL (code: A337, base: A332) from:
> **[Airbus Aircraft SimBrief Profiles for Microsoft Flight Simulator 2024](https://forum.inibuilds.com/topic/24033-airbus-aircraft-simbrief-profiles-for-microsoft-flight-simulator-2024/)**
>
> Hello! We hope you're excited for the latest aircraft coming to the simulator! We’ve taken the time to create some accurate SimBrief profiles for those who want to ensure accurate flight planning and get the most accurate performance data. Whether...
LIDO
```txt
F-WWMT 19SEP2026 LSGG-CYVR A400 FWWMT RELEASE 2045 19SEP26
F-GXLG 19SEP2026 LSGG-CYVR A337 FGXLG RELEASE 2046 19SEP26
```
But it also happens with other (presumably all) _default_ profiles where the base type and ICAO do not match:
SR2T (should be S22T)
```txt
N226SB 19SEP2026 LSGG-CYVR SR2T N226SB RELEASE 2050 19SEP26
```
E13L (should be E35L)
```txt
N132SB 19SEP2026 LSGG-CYVR E13L N132SB RELEASE 2052 19SEP26
```
BBJ1 (should be B737) and presumably other BBJs
```txt
N700SB 19SEP2026 LSGG-CYVR BBJ1 N700SB RELEASE 2053 19SEP26
```
B74F (should be B744)
```txt
N487SB 19SEP2026 LSGG-CYVR B74F N487SB RELEASE 2054 19SEP26
```
B48F used instead of B748, B75F instead of B752, B77F instead of B77L, etc. etc.
The ICAO flight plan portion of the briefing is unaffected by this issue.
Regards,
Tim
---
### Author:  [@SimBrief](https://forum.navigraph.com/u/SimBrief)
#### Post date: [September 23, 2026, 3:03pm UTC](https://forum.navigraph.com/t/default-profiles-base-type-unexpectedly-used-in-place-of-icao-type-designator/24332/2 "2026-09-23T15:03:15Z")
Hi Tim, IIRC this is intentional. Many airlines use their own internal type codes in their OFP headers.
One common example in real world OFPs would be winglet vs non-winglet aircraft, B738 vs B73W as an example. Similarly, it can be useful to display the SimBrief internal type code for aircraft that have marked performance differences, yet share the same ICAO code. For example the AC11/AC1T, BE60/BE6G, C182/R182, DA40/DA4N, P180/P18E, etc.
With that said, custom aircraft types in SimBrief (those added purely via custom airframe, i.e. A400, A337) are handled a bit differently. Since the point of these airframes is to simulate an otherwise unsupported aircraft, we don’t show the original base type as that would break immersion.
Best regards,