ZBTJ - ILS 34L is not aligned with the runway

Bug Reporting Hub ATC, Traffic & NAVAIDs
, , ,
1

ISSUE DESCRIPTION

Description of the issue: ZBTJ - ILS 34L is not aligned with the runway

If applicable, which aircraft is experiencing this issue:
A330

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
No

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

It will appear at half of the airports where you land.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Landing at Tianjin Binhai International Airport
  2. ICAO code: ZBTJ
  3. runway: 34L
    image
    image779×1008 126 KB

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

[PC Only] Are you using Developer Mode or have you made any changes to it?
No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use?
GTX1660Ti

[PC Only] What other relevant PC specs can you share?
No

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

IMG_0874
IMG_08741920×2560 432 KB

2

Hi @BOEINGNG ,

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

3

Could you provide more information on that airport ?, like ICAO code, runway used, approach chart ?
Some airports have offset ILS so it is not always a bug.

1 Like
4

I’m not the OP but the airport is ZBTJ. It has ILS approaches to runway 16L and R and 34L and R. None have offset localizers per Navigraph charts

5

Thank you @HalberQuacky !

@BOEINGNG : could you please add missing information to the template (ICAO, runway(s) you are having an issue with, all useful information in order for the devs and community to be able to reproduce the issue), so that we can move back the report to the Bug Reporting Hub .

6

Here’s LNM’s distillation of runway data for ZBTJ. Confirms Localisers are aligned with runways.
This was extracted from MSFS 2020 navdata though.
I’ll try it in 2024 when I can.

Little NavMap Summary 
  Binhai (ZBTJ)  Map, Procedures
Elevation: 5 ft

Runways 16L, 34R
Size:
10,492 x 137 ft
Surface:
Cement
Pattern Altitude:
1,000 ft
Edge Lights:
High
Center Lights:
High
Runway Markings:
Edges, Threshold, Fixed Distance, Touchdown, Dashes, Ident, Precision, Alternate Touchdown

Runway 16L
Heading:
162°M
Blast Pad:
200 ft
Pattern:
Left
ILS, GS, DME ICU
Frequency:
109.70 MHz
Magnetic declination:
7.7° West
Range:
27 NM
Morse:
· ·   − · − ·   · · −
Has Backcourse
 
Localizer Heading:
162°M
Width:
3.48°
Glideslope:
3.0°

Runway 34R
Closed
 
Heading:
342°M
Blast Pad:
196 ft
Pattern:
Left
Left VASI Type:
PAPI4
Left VASI Pitch:
3.0°
ILS, GS, DME IKD
Frequency:
111.50 MHz
Magnetic declination:
7.7° West
Range:
27 NM
Morse:
· ·   − · −   − · ·
Has Backcourse
 
Localizer Heading:
342°M
Width:
3.51°
Glideslope:
3.0°


Runways 16R, 34L
Size:
11,804 x 151 ft
Surface:
Asphalt
Pattern Altitude:
1,000 ft
Edge Lights:
High
Center Lights:
High
Runway Markings:
Edges, Threshold, Fixed Distance, Touchdown, Dashes, Ident, Precision, Alternate Touchdown

Runway 16R
Heading:
162°M
Offset Threshold:
1,315 ft
Available Distance for Landing:
10,489 ft
Pattern:
Left
ALS Type:
ALSF1
Runway End Lights:
Lights
ILS, GS, DME IJS
Frequency:
110.90 MHz
Magnetic declination:
7.7° West
Range:
27 NM
Morse:
· ·   · − − −   · · ·
Has Backcourse
 
Localizer Heading:
162°M
Width:
3.41°
Glideslope:
3.0°

Runway 34L
Heading:
342°M
Pattern:
Left
ALS Type:
ALSF1
Runway End Lights:
Lights
ILS, GS, DME ICG
Frequency:
110.50 MHz
Magnetic declination:
7.7° West
Range:
27 NM
Morse:
· ·   − · − ·   − − ·
Has Backcourse
 
Localizer Heading:
342°M
Width:
3.12°
Glideslope:
3.0°

Airport has no helipad.
Start Positions
Runway 16L, Runway 16R, Runway 34L, Runway 34R
7

This is a problem with the navdata: runway and ils are misaligned by 7 degrees.
I have no idea of the situation IRL.
But the magnetic declination for the area is 7.7 degrees, so there’s a clue, maybe.

ils
ils1920×1080 226 KB

Edit to add:
Turns out the runway headings in he EFB are always degrees true, not magnetic. So that accounts for that discrepancy.
Something fishy going on but I don’t know what.

8

OK, I have added.

1 Like
9

The magnetic declination may be mistakenly regarded as the angle between the ILS Loc and the runway.

10

Title updated with ICAO & RWY # for better clarity and easy search. Moved back to Bug Reporting Hub .

11

Yes, something like that.
But the localiser track for both of us is 341 or 342 magnetic, which is correct.
It’s like the runway has been painted on the ground wrong…