Skip to content

上海进近SOP 调整程序代号及其他内容#54

Open
AaronZSAM101 wants to merge 2 commits into
VATPRChina:mainfrom
AaronZSAM101:dev/2606-ZSSS
Open

上海进近SOP 调整程序代号及其他内容#54
AaronZSAM101 wants to merge 2 commits into
VATPRChina:mainfrom
AaronZSAM101:dev/2606-ZSSS

Conversation

@AaronZSAM101

@AaronZSAM101 AaronZSAM101 commented Jun 23, 2026

Copy link
Copy Markdown
Contributor
  1. 调整程序代号,新增虹桥进离场主用程序,新增浦东进场主用程序和跑道
  2. 新增虹桥机场航路PMS工作流程
  3. 删除扬州、常州的按需服务内容

@github-actions
github-actions Bot requested a review from ZBAA-LucasF June 23, 2026 18:19
@AaronZSAM101 AaronZSAM101 changed the title feat(*): 调整程序代号及其他内容 上海进近SOP 调整程序代号及其他内容 Jun 23, 2026

> 呼号,上海进近雷达看到了,SASAN-X 程序进场,**xxx过渡**,跑道xx”
>
> Callsign, Shanghai Approach radar contact, follow SASAN-x arrival, xxx transition, runway xx.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

“x”等需要按情况填空的内容应当使用标点标注出来

| 离场点 | 主用跑道 | 离场程序 |
| :----: | :------: | :------: |
| ADBAS | 36L/18R | ADBAS-8 |
| PIKAS | 36L/18R | PIKAS-8 |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PIKAS北向离场建议使用PIKAS-9控制转弯位置,避免与SASAN方向进场程序产生水平航迹交叉风险

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

不会,本身初始上高就不会给太高

| AND | 36L/18R | AND-Z |
| PONAB | 36L/18R | PONAB-9 |
| MIGOL | 36L/18R | MIGOL-8 |
| LAMEN | 36L/18R | LAMEN-8 |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LAMEN方向建议参考航路走向分配LAMEN-8与LAMEN-9实现分流


上海虹桥机场主用RNAV程序,无法使用RNAV程序的,塔台管制员应当与进近管制员协调使用传统程序或采用雷达引导离场。

###### 离场

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

目前方案所有向东离场全部需要从本场南侧通过,与SASAN、庵东方向进场航迹存在交叉,缺乏对北侧空域的利用


| 进场点 | 主用跑道 | 离场程序 |
| :----: | :------: | :------: |
| AND | 35L | AND-2 |

@LotinZhang LotinZhang Jun 24, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

庵东并非进场主用程序


| 进场点 | 主用跑道 | 离场程序 |
| :----: | :------: | :------: |
| AND | 17R | AND-1 |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

庵东并非进场主用程序

#### 2.3.1 无锡硕放机场

适用范围:无锡机场起降往返经上海终端管制区的航班,由无锡进近与上海进近进行管制移交。无锡进近管制空域可由上海进近代管,由上海进近按需指挥。
无锡机场起降往返经上海终端管制区的航班,由无锡进近与上海进近进行管制移交。无锡进近管制空域可由上海进近代管,由上海进近按需指挥。

@LotinZhang LotinZhang Jun 24, 2026

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

按当前运行规章规定,无锡进近管制区、宁波进近管制区、嘉兴塔台管制区、舟山塔台管制区等在没有相应席位时,强制要求上海进近对其进行管制,而非可以代管。本条规定与运行规章存在冲突。


| 登录名 | 呼号 | 频率 | 职责范围 |
| :--------: | :------: | :----: | :-----------------------------------------------------------------: |
| ZSSS_E_APP | 上海进近 | 127.75 | 浦东MATNU/DUMET进场调配,虹桥PUD进场排序,东向南向离场调配。AP08/10 |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

管制范围需要文字描述垂直范围,同时配图,不能仅用扇区号码。不然一眼都看不出来垂直范围多高。

##### 进扇区

| 移交点 | 相对位置 | 航线 | 移交高度/百米 | 上级席位 |
| :---------: | :------: | :----------------------------: | :-----------: | :------: |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

移交席位应当使用登录名描述

| 进场点 | 主用跑道 | 离场程序 |
| :----: | :------: | :------: |
| AND | 35L | AND-2 |
| BK | 34R | BK-2 |

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BK-2程序为东三边,不宜主用34R

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants