Skip to main content

Summary

Developer: DACC
Sponsor Organization: CAPP
Current Status: Out for final 30-day industry review. Closes November 12, 2026. 
Feedback: To provide feedback or comments regarding the IRP 22 Draft or any of the defined terms, please use the Feedback Form and send it to [email protected]

This update reflects a limited-scope review of IRP 22 to align with updates to API 92M, particularly regarding dynamic influx management, definition standardization, and MPD training considerations. Revisions are intended to clarify expectations and reduce ambiguity without significantly changing the overall intent of the IRP.

Key elements addressed during the final round of edits include:

  • 22.6.2 Determination of Safe Operating Limits For Influx Management for MPD Operations 
  • 22.6.3 Influx Detection, Control and Circulation Using MPD Equipment
  • 22.16.7 Managed Pressure Cementing and the use of solid body mandrels

Overview

This update reflects a limited-scope review of IRP 22 to align with updates to API 92M, particularly regarding dynamic influx management, definition standardization, and MPD training considerations. Revisions are intended to clarify expectations and reduce ambiguity without significantly changing the overall intent of the IRP.

Key objectives of this update include:

  • Improve clarity and consistency in operations practices (e.g., influx detection, mitigation, and tripping/stripping),
  • Align influx management concepts and terminology with current API guidance (including dynamic influx management),
  • Enhance guidance for surface systems and equipment (e.g., pressure management, overpressure protection, and equipment expectations), and
  • Incorporate considerations for MPD-specific practices such as tripping, managed pressure dementing, and training expectations.

A detailed list of revisions is provided in Appendix A: Revision Log, Table 8 Edition 4 Revisions.

Supplemental Resources

Process Flow Diagrams

Have feedback or questions?

We welcome your input. Send your comments to [email protected]

Share: