SF-50 Retirement Code Air Traffic Controller: How to Read Block 30

The One Box on Your SF-50 That Controls Your Pension

Every personnel action in your federal career generates a Standard Form 50. Most controllers glance at the pay figures and move on. Block 30 — labeled "Retirement Plan" — is the field that actually determines whether each year of your career earns the enhanced 1.7% annuity multiplier or the standard 1.0% rate.

A miscoded Block 30 during a period of covered ATC service doesn't just reduce your pension calculation. It can prevent OPM from recognizing those years toward the 20-year eligibility threshold under 5 U.S.C. § 8412(e). Controllers have discovered during their retirement application that years they assumed were "good time" were coded as standard FERS — turning a clean retirement into a months-long correction process.

Block 30 Codes and What They Mean

Code L — FERS Special Category (pre-2013 hires): Covered. Employee contribution rate of 1.3%. This is the correct code for controllers hired before January 1, 2013 who are in covered ATC positions.

Code M — FERS-RAE Special Category (2013 hires): Covered. Employee contribution rate of 3.6%. Correct for controllers first hired between January 1, 2013 and December 31, 2013.

Code K — FERS-FRAE Special Category (post-2013 hires): Covered, but this is where miscodings happen most often. The employee contribution rate for Special Category FERS-FRAE is 4.9%. Standard FERS-FRAE employees also use Code K but pay 4.4%. If your pay stub shows a 4.4% FERS deduction instead of 4.9%, your position may be coded as standard rather than special category — even though the letter code looks the same.

Code 6 — CSRS Special Category: Covered under the older Civil Service Retirement System provisions. Employee contribution rate of 7.5%.

Standard FERS codes (Code K at 4.4%, Code E): Not covered. These codes mean the position is classified as standard federal service. Pension credit accrues at 1.0%, and the time does not count toward the 20-year ATC threshold.

How to Check Your Full History

Access your complete SF-50 history through:

• FAA employees: The electronic Official Personnel Folder (eOPF) system
• DoD employees: Defense Civilian Personnel Data System (DCPDS) or MyBiz

Pull every personnel action from your career start date to present. For each SF-50, check Block 30 against the codes above. Pay special attention to:

• Position changes: Any time you moved between facilities, changed roles, or took a promotion. These are the most common points where miscoding occurs.
• Organizational restructurings: When facilities reorganize or positions are reclassified, HR sometimes processes the new action under a standard code.
• Post-2013 hires: The Code K overlap between standard and special category FERS-FRAE makes miscodings harder to catch visually. Verify by checking your payroll deduction rate — 4.9% confirms special category, 4.4% means standard.

What to Do If a Code Is Wrong

If any SF-50 shows a standard FERS code during a period when you were performing covered ATC duties:

1. Document the discrepancy: Record the specific SF-50 effective dates, the incorrect code, and what the code should be based on your position duties.

2. Contact your agency HR office: File a formal request for a personnel action correction. Provide your position description and any operational documentation showing you were actively engaged in traffic separation or direct supervision of controllers.

3. Request a position coverage determination: This is the official agency review of whether your position meets the statutory definition under 5 U.S.C. § 2109. The determination will either confirm or deny Special Category coverage for the disputed period.

4. Keep your own records: Don't rely solely on the electronic system. Save copies of every SF-50, the correction request, and the agency's response. If you need to appeal, this documentation is essential.

5. Appeal if denied: You have 30 calendar days from the agency's final decision to appeal to the Merit Systems Protection Board under 5 CFR 842.807.

Common Miscoding Scenarios

Facility transfer delays: When transferring between facilities, a gap in personnel processing can result in the new SF-50 being issued under a standard code, especially if the gaining facility's HR office doesn't flag the special category requirement.

Supervisory promotions: Promotion to a first-level or second-level supervisory position should maintain special category coding — but HR must affirmatively classify the position as covered. If they don't, the default is often standard FERS.

System migrations: When HR systems are updated or migrated, historical data can be incorrectly mapped. Controllers who started in the eOPF era sometimes find that earlier records were converted with standard codes.

Timing Matters

Correcting a miscoded SF-50 is straightforward before retirement — a personnel action fix with supporting documentation. After you've separated and your file is at OPM, corrections require coordination between your former agency and OPM's Retirement Operations Center, adding months to processing.

Audit your Block 30 codes now, while you're still on the payroll and your HR office is accessible. The Air Traffic Controller Retirement Guide includes a Covered-Service Audit Worksheet designed specifically for walking through every SF-50 in your history, line by line, to catch discrepancies before they reach OPM.

See more United States guides →