Brief Case
Pension Resource

29 C.F.R. § 4203.5

PBGC action on requests.
eCFR editorial change effective 2017-01-01 · current
PrintCompare datesAsk AI about this sectionOfficial source ↗
(a) General. The PBGC shall approve a plan amendment providing for the application of special complete or partial withdrawal liability rules upon a determination by the PBGC that the plan amendment—
(1) Will apply only to an industry that has characteristics that would make use of the special withdrawal rules appropriate; and
(2) Will not pose a significant risk to the insurance system.
(b) Notice of pendency of request. As soon as practicable after receiving a request for approval of a plan amendment containing all the information required under § 4203.4, the PBGC shall publish a notice of the pendency of the request in the Federal Register. The notice shall contain a summary of the request and invite interested persons to submit written comments to the PBGC concerning the request. The notice will normally provide for a comment period of 45 days.
(c) PBGC decision on request. After the close of the comment period, PBGC shall issue its decision in writing on the request for approval of a plan amendment. Notice of the decision shall be published in the Federal Register.
29 C.F.R. § 4203.5 — PBGC action on requests. · eCFR editorial change effective 2017-01-01 · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-4203.5 · printed Oct 16, 2026
On this page
  • (a) General.
  • (b) Notice of pendency of request.
  • (c) PBGC decision on request.
Implements
ERISA § 4203 (29 U.S.C. § 1383) Complete withdrawal

No guidance in the library cites this section yet.

No court rulings in the library cite this provision yet.

No private letter rulings in the library cite this provision yet.

Each row is a version of the text as published by the official source. Code dates are the edition/release point that first reflected the change; regulation dates are eCFR effective dates. The library checks the official sources automatically, so new versions appear here on their own; “run” opens the sync that recorded a version.

EffectiveThroughSourceAmended by
Jul 1, 1997currenteCFR editorial change effective 2017-01-01 run 2View
Provision-level history (blame)