Brief Case

29 C.F.R. § 4204.22

PBGC action on requests.
eCFR editorial change effective 2017-01-01 · current
(a) General. The PBGC shall approve a request for a variance or exemption if PBGC determines that approval of the request is warranted, in that it—
(1) Would more effectively or equitably carry out the purposes of title IV of ERISA; and
(2) Would not significantly increase the risk of financial loss to the plan.
(b) Notice of pendency of request. As soon as practicable after receiving a variance or exemption request containing all the information specified in § 4204.21, the PBGC shall publish a notice of the pendency of the request in the Federal Register. The notice shall provide that any interested person may, within the period of time specified therein, submit written comments to the PBGC concerning the request. The notice will usually provide for a comment period of 45 days.
(c) PBGC decision on request. The PBGC shall issue a decision on a variance or exemption request as soon as practicable after the close of the comment period described in paragraph (b) of this section. PBGC's decision shall be in writing, and if the PBGC disapproves the request, the decision shall state the reasons therefor. Notice of the decision shall be published in the Federal Register.
29 C.F.R. § 4204.22 — PBGC action on requests. · eCFR editorial change effective 2017-01-01 · https://pensionresource.website/EAMain?content=EAMain.Law&id=cfr29-4204.22 · printed Oct 16, 2026
On this page
  • (a) General.
  • (b) Notice of pendency of request.
  • (c) PBGC decision on request.
Implements

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)