Airworthiness Directives: Pratt and Whitney Division Engines
Details
The document's own metadata, straight from the source system.
- Title
- Airworthiness Directives: Pratt and Whitney Division Engines
- Posted
- May 26, 2026
- Comment period
- May 26, 2026 – Jul 11, 2026
- FR Doc
- 2026-10408
- CFR
- 14 CFR Part 39
- Topics
Overview
What the public is saying — stance, who's commenting, and the issues they raise.
Stance breakdown
Who commented
Breakdown by commenter type.
Comments over time
Weekly arrivals, stacked by stance.
Support × commenter type
How each type splits across stance.
Issues raised
The docket's canonical issues. Select one to browse its comments.
Position map
Who stands where on each issue?
Every non-silent position is backed by an excerpt from the comment.
Issues shown
Choose up to five.
| Organization | Sensor replacement requirements | Years in service definition |
|---|---|---|
Delta Air Lines BusinessSupport Delta Air Lines, Inc. | · | |
Pratt & Whitney, an RTX Business BusinessSupport Pratt & Whitney (RTX Corporation) supports the proposed Airworthiness Directive but requests specific technical clarific | · |
Explorer
Every mirrored comment — filter by stance, campaign, or issue.
- Jul 8, 2026United Parcel Service (UPS)SupportBusiness
UPS Airlines requests specific modifications to the compliance methods for the Airworthiness Directives regarding Pratt and Whitney Division Engines. They propose allowing a 15-year calendar-time compliance interval for low-utilization operators and seeking a method to determine replacement timeframes for sensors with unknown history.
Read comment → - Jul 7, 2026United AirlinesSupportBusiness
United Airlines supports the Airworthiness Directive but requests the inclusion of specific Accomplishment Instructions from a Pratt & Whitney Service Bulletin. They argue that because EEC timers can be unreliable, the AD should allow for calculating operational hours based on years in service or average annual utilization.
Read comment → - Jun 21, 2026Atlas AirSupportBusinessRead comment →
