<!doctype html>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" lang="en-US" xml:lang="en-US">
  <head>
    <title data-ignore-plain-text>CRC Regulatory Update</title>
    <meta http-equiv="content-type" content="text/html; charset=utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">
    <meta name="format-detection" content="address=no">
    <!--[if (gte mso 9)|(IE)]>
    <style type="text/css" media="screen">
      li {
        text-indent: -1em;
      }
    </style>
    <![endif]-->
    <style type="text/css" media="all">
      body,
.section-text-area,
.section-text-area-wrapper,
.section-text-cell {
    overflow-wrap: break-word;
    word-wrap: break-word;
    -ms-word-break: break-all;
    word-break: break-word;
}
body {
    width: 100% !important;
    min-width: 100% !important;
    -ms-text-size-adjust: none;
    -webkit-text-size-adjust: none;
    mso-line-height-rule: exactly;
}
p {
    margin-block: 0;
}
@media only screen and (max-width:  593px ) {
    table#newsletter-table {
        border: 0 !important;
    }
    table#newsletter-email {
        width: 100% !important;
    }
    img.section-scaleable-image,
    img.section-empty-img {
        max-width: 100% !important;
        height: auto !important;
    }
    .bg-none {
        background: none !important;
    }
    .hauto {
        height: auto !important;
    }
    .show-desktop-only {
        display: none !important;
    }
    .show-mobile-only {
        display: block !important;
        float: none !important;
        line-height: auto !important;
        max-height: inherit !important;
        max-width: inherit !important;
        margin-top: 0px !important;
        overflow: visible !important;
        visibility: inherit !important;
        width: auto !important;
    }
    .stack-cell-wrap {
        display: block !important;
    }
    .stack-cell-up {
        display: table-header-group !important;
    }
    .stack-cell-down {
        display: table-footer-group !important;
    }
    .mw100p {
        max-width: 100% !important;
    }
    .section-horizontal-padding,
    .padding-mobile-both {
        padding-left: 22px !important;
        padding-right: 22px !important;
    }
    .padding-mobile-left {
        padding-left: 22px !important;
    }
    .padding-mobile-right {
        padding-right: 22px !important;
    }
    .text-left {
        text-align: left !important;
    }
    .text-right {
        text-align: right !important;
    }
    .w100p {
        width: 100% !important;
    }
}
.button-style-solid:hover,
.button-style-rounded:hover {
    opacity: .8 !important;
}
a:hover {
    text-decoration: none !important;
}
span.mail-merge-preview {
    border-bottom: 2px dotted currentColor;
    display: inline-block;
    line-height: 1em !important;
    margin-bottom: .125em !important;
}
table#newsletter-section-body .linked-site-title-link {
    color: #064489 !important;
}
#header-header-section-stacked-top-0 .brand-name .linked-site-title-link {
    color: #fff;
    text-decoration: none;
}
#footer-footer-section-stacked-top-0 .brand-name .linked-site-title-link {
    color: #444b50;
    text-decoration: none;
}
#footer-footer-section-stacked-top-0 .footer-text .linked-site-title-link {
    color: #064489;
}
body.renderedPreview #line-line-section-6 div.basic-line[data-line="dashed"] {
    border-width: .5px 0 !important;
}
body.renderedPreview #line-line-section-9 div.basic-line[data-line="dashed"] {
    border-width: .5px 0 !important;
}
body.renderedPreview #line-line-section-12 div.basic-line[data-line="dashed"] {
    border-width: .5px 0 !important;
}
body.renderedPreview #line-line-section-15 div.basic-line[data-line="dashed"] {
    border-width: 1px 0 !important;
}
#button-button-section-19 .button-style-outline:hover {
    background-color: #fff !important;
    border: 1px solid #fff !important;
}
#button-button-section-19 .button-style-outline:hover .button-section-label {
    color: #000 !important;
}

    </style>
    
    
    <!--[if mso]>
    <noscript>
      <xml>
        <o:OfficeDocumentSettings>
          <o:AllowPNG/>
          <o:PixelsPerInch>96</o:PixelsPerInch>
        </o:OfficeDocumentSettings>
      </xml>
    </noscript>
    <![endif]-->
    
    <!--[if (mso)|(mso 16)]>
      <style type="text/css">
        a {text-decoration: none;}
      </style>
    <![endif]-->
  </head>
  <body style="padding:0;margin:0;text-align:center;background-color:#f6f6f6;">
    <table role="article" aria-label="CRC Regulatory Update" lang="en-US" cellpadding="0" cellspacing="0" border="0" align="center" id="newsletter-table" style="font-size:16px;font-weight:normal;width:100%;padding:0px;background-color:#f6f6f6;border-top:44px solid #f6f6f6;border-bottom:44px solid #f6f6f6;margin:0 auto;text-align:center;table-layout:fixed;">
  <tbody><tr>
    <td align="center" valign="top" bgcolor="#F6F6F6" id="newsletter-cell" style="font-size:1em;">
      <div data-ignore-plain-text class="newsletter-preview-text" style="color:transparent;display:none !important;height:0;max-height:0;max-width:0;opacity:0;overflow:hidden;mso-hide:all;visibility:hidden;width:0;">
        
            
            Rulemaking activities for your attention͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;͏‌&nbsp;
        
      </div>
      <table border="0" cellpadding="0" cellspacing="0" width="594" bgcolor="#FFFFFF" id="newsletter-email">
        <tbody><tr>
          <td align="center" valign="top" id="newsletter-email-wrapper" class="book-sans">
            <table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" id="newsletter-section-header">
              <tbody><tr>
                <td align="center" valign="middle" id="newsletter-section-header-cell">
                  
<div id="header-header-section-stacked-top-0">





<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#F6F6F6" class="section-content header-section header-section-stacked" style="background-color:#f6f6f6;">
  <tbody><tr>
    <td align="center" valign="middle" class="section-text-area section-content-cell" style="padding-top:19px;padding-right:0px;padding-bottom:18px;padding-left:0px;">
      
  <p class="brand-name" style="margin:0 0 1.25em 0;font-weight:normal;height:1.618em;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;color:#fff;font-size:9px;line-height:1em;mso-line-height-alt:9px;white-space:pre-wrap;"></p>
  
  

      
    </td>
  </tr>
</tbody></table>

</div>
                </td>
              </tr>
            </tbody></table>
            <table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" id="newsletter-section-body">
              <tbody><tr>
                <td align="center" valign="top" width="100%" id="newsletter-section-body-cell">
                  
<div id="image-image-section-below-0">
<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="transparent" class="image-section below-layout section-content">

  

  
    <tbody><tr>
      <td>
        <table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0">
          <tbody><tr>
              

            <td align="left" valign="middle" class="section-image-cell section-content-cell section-hoverable-image" data-aspect="ORIGINAL" style="padding:0;">
              
  <img class="section-scaleable-image" src="https://images.squarespace-cdn.com/content/64308e1bd95e74741ca4f52a/50330878-6235-4026-b9bf-b46c1d0af6b5/Regulatory+Update+Banner+2.png?content-type=image%2Fpng&amp;format=750w" width="594" alt="" style="font-size:.8em;display:block;border:0;text-decoration:none;line-height:0;background-color:transparent;font-weight:normal;height:auto;width:100%;max-width:100%;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">


            </td>
              

          </tr>
        </tbody></table>
      </td>
    </tr>
    
  
  


</tbody></table>

</div>
<div id="text-text-section-1">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#E0E0DB" class="text-section section-content">
  <tbody><tr>
    <td valign="top" class="section-text-area section-content-cell" style="padding-top:19px;padding-right:11px;padding-bottom:11px;padding-left:11px;color:#000;background-color:#e0e0db;">
      <p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><em><strong>Devin Rouse, DC Rail Advisory &amp; CRC Regulatory Advisor</strong></em></p><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">It’s been quiet for quite some time on the railroad safety regulatory front, but as expected, the flood gates opened before the election, and we have a number of new proposed rulemakings to consider that will directly impact commuter railroads. Unfortunately, because of the timing, the comment period for these will coincide with the holidays and year end activities. So its critical that we determine what, if any comments we want to submit to articulate any suggestions or concerns from the commuter railroad perspective. With that in mind, we encourage our members, and in particular, our commuter railroads, to have their relevant subject matter experts review the proposed rulemakings and determine if there are comments that should be submitted by CRC.  Specifically, we have provided questions relevant to each rule that we would invite members to provide feedback on, below.</p><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">In addition to the rulemaking discussions, we have a number of other updates to provide, including a summary of the most recent RSAC meeting. So as to not overload you with too much information this month, we will provide more detail on some of these other regulatory matter in next month’s update.</p>
    </td>
  </tr>
</tbody></table>

</div>
<div id="spacer-spacer-section-2">

<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="transparent" class="spacer-section section-content">
  <tbody><tr>
    <td align="center" valign="middle" class="section-content-cell" height="22" style="height:22px;">
    </td>
  </tr>
</tbody></table>

</div>
<div id="text-text-section-3">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#2A2829" class="text-section section-content">
  <tbody><tr>
    <td valign="top" class="section-text-area section-content-cell padding-mobile-both" style="padding-top:8px;padding-right:66px;padding-bottom:8px;padding-left:66px;color:#fff;background-color:#2a2829;">
      <h4 style="color:inherit;margin:1.414em 0 .5em;font-weight:400;line-height:1.25em;font-size:1.25em;mso-line-height-alt:1.25em;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;letter-spacing:.02em;text-align:center;"><strong>RULEMAKING ACTIVITIES</strong></h4>
    </td>
  </tr>
</tbody></table>

</div>
<div id="text-text-section-4">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="transparent" class="text-section section-content">
  <tbody><tr>
    <td valign="top" class="section-text-area section-content-cell padding-mobile-both" style="padding-top:8px;padding-right:66px;padding-bottom:8px;padding-left:66px;color:#253551;background-color:transparent;">
      <h4 style="color:inherit;margin:1.414em 0 .5em;font-weight:400;line-height:1.25em;font-size:1.25em;mso-line-height-alt:1.25em;margin-top:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;letter-spacing:.02em;text-align:center;"><em><strong>FINAL RULES</strong></em></h4><h4 style="color:inherit;margin:1.414em 0 .5em;font-weight:400;line-height:1.25em;font-size:1.25em;mso-line-height-alt:1.25em;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;letter-spacing:.02em;text-align:center;"><strong>Part 245 &amp; 246 Certification Rules – Petitions for Reconsideration and FRA Q&amp;A</strong></h4>
    </td>
  </tr>
</tbody></table>

</div>
<div id="text-text-section-5">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#FFFFFF" class="text-section section-content">
  <tbody><tr>
    <td valign="top" class="section-text-area section-content-cell" style="padding-top:19px;padding-right:11px;padding-bottom:11px;padding-left:11px;color:#253551;background-color:#fff;">
      <p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">As many of you are aware, CRC submitted a Petition for Reconsideration to FRA on July 12, 2024, to voice concerns over certain aspects of the dispatcher (49 CFR Part 245) and signal employee (40 CFR Part 246) certification rules. The petition touched on a number of points that have been raised by CRC members over the past year including the timeframe for program development and implementation, logistical challenges related to execution of the rule, and the impracticality of application and oversight of the requirements to third party contractors. CRC’s petition can be downloaded <a href="https://www.regulations.gov/document/FRA-2022-0019-0047" rel="nofollow" style="color:#064489 !important;">here</a>.</p><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">Many CRC members also participated and contributed to a formal Q&amp;A document that raised similar questions for additional clarity regarding both rulemakings. CRC held a Q&amp;A session with FRA on July 2, 2024, and submitted formal questions to FRA on July 29, 2024. We originally discussed an estimated turn-around for the Q&amp;A document by Labor Day, however, we expect that industry’s submissions of petitions for reconsideration have offset this outlook. Several of the questions are tied directly to matters raised in the petition documents, so if FRA does choose to formally modify any of the regulatory requirements, it could supersede the responses to some of CRC’s questions.</p><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">CRC is currently working with FRA to set up a meeting to discuss and provide practical examples of the challenges its members are facing attempting to implement the final rule. We hope that this perspective can help illustrate the importance behind many of the points raised in our petition. We will be working with interested members to either participate or provide their insight into these discussions. Most importantly, if you have any additional questions regarding the implementation of Parts 245 or 246, please submit them to us as soon as possible, so that we can incorporate them into any discussions that are held.</p>
    </td>
  </tr>
</tbody></table>

</div>
<div id="line-line-section-6">

<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="transparent" class="line-section section-content">
  <tbody><tr>
    <td align="center" valign="middle" width="100%">
      <table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" class="line-section-table section-content" style="width:20%;min-width:20%;">
        <tbody><tr>
          <td align="center" valign="middle" class="section-content-cell" width="100%" style="padding-top:22px;padding-right:0;padding-bottom:22px;padding-left:0;">
            <div class="basic-line" data-line="solid" style="background:none;font-size:0;margin:0;line-height:0;height:0;width:100%;border-style:solid none;border-width:1px 0 0px;border-color:#000;">&nbsp;</div>
          </td>
        </tr>
      </tbody></table>
    </td>
  </tr>
</tbody></table>

</div>
<div id="text-text-section-7">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#E0E0DB" class="text-section section-content">
  <tbody><tr>
    <td valign="top" class="section-text-area section-content-cell" style="padding-top:8px;padding-right:20px;padding-bottom:8px;padding-left:20px;color:#313131;background-color:#e0e0db;">
      <h4 style="color:inherit;margin:1.414em 0 .5em;font-weight:400;line-height:1.25em;font-size:1.25em;mso-line-height-alt:1.25em;margin-top:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;letter-spacing:.02em;text-align:center;"><em><strong>NOTICES OF PROPOSED RULEMAKING (NPRM)</strong></em></h4><h4 style="color:inherit;margin:1.414em 0 .5em;font-weight:400;line-height:1.25em;font-size:1.25em;mso-line-height-alt:1.25em;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;letter-spacing:.02em;text-align:center;"><strong>Positive Train Control Systems – Amendments to Part 236 [Docket # FRA–2023–0064]</strong></h4>
    </td>
  </tr>
</tbody></table>

</div>
<div id="text-text-section-8">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#E0E0DB" class="text-section section-content">
  <tbody><tr>
    <td valign="top" class="section-text-area section-content-cell" style="padding-top:19px;padding-right:11px;padding-bottom:11px;padding-left:11px;color:#000;background-color:#e0e0db;">
      <p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">On October 28th, FRA published the anticipated proposed amendments to Part 236. These amendments would modify certain provisions governing temporary situations during which PTC technology is not enabled, including after certain initialization failures, or in cases where a PTC system needs to be temporarily disabled. Specifically, the NPRM proposes to revise the following sections within the current PTC regulations contained in Subpart I to 49 CFR Part 236:</p><ul data-rte-list="default" style="padding-left:25px;"><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><em>§ 236.1006 Equipping locomotives operating in PTC territory –</em> FRA is proposing to add an exemption under paragraph (b) to accommodate certain non-revenue moves of passenger equipment to a point of repair. The move can only be made solely for the purpose of repairing or exchanging a PTC system, so long as such moves comply with six proposed conditions (e.g., limited speed, absolute block, prohibition of work zones, etc.).</p></li><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><em>§ 236.1021 Discontinuances, material modifications, and amendments –</em> Here, FRA is proposing to clarify requirements to temporarily disable a PTC system when necessary to facilitate repairs or maintenance, upgrade or modify infrastructure, or implement capital projects that require a temporary system outage. Prior to December 31, 2022, railroads were permitted to temporarily disable PTC systems when necessary to perform such work, so long as they notified the appropriate FRA regional office in advance. When this provision expired, such outages could only be permitted through a formal Request for Amendment (RFA). The proposed language, retains the requirement for an approved RFA, but is aimed at streamlining RFA requests to disable PTC on an equipped section of track for the reasons cited above.</p></li><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><em>§ 236.1029 PTC system use and failures –</em> In this section, FRA is proposing to effectively reintroduce operational flexibility for certain types of initialization failures, specifically, systemic failures in which multiple trains are impacted. As FRA notes in the NPRM “this section does not apply to a single train that experiences an onboard PTC system failure at the initial terminal…[t]he purpose of this paragraph (g) is to address issues affecting multiple trains.” Under this new provision, a railroad would be able to permit the movement when a system-wide failure inhibits the ability for trains to initialize, and requires certain operating restrictions that would become increasingly restrictive after the first 24 hours.</p></li></ul><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">The changes proposed largely follow the areas previously identified by FRA in its meetings with industry, and appear to have adopted a number of the points raised in those discussions. The CRC plans to examine the points raised from our previous meetings and compare them against the proposed language. Specifically, CRC is interested in its member’s perspectives regarding the following:</p><ul data-rte-list="default" style="padding-left:25px;"><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">Does the proposed language in § 236.1006(b)(6) sufficiently address the types of non-revenue movements required by passenger operators, or is the language too limiting?</p></li><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">Has the RFA process proven to be timely and manageable for railroads that have implemented temporary outages using this process? Would the proposed streamlining in § 236.1021(m)(4) help as written, or should other factors be considered?</p></li><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">Is the 24-hour initial operational flexibility provided in § 236.1029(g) enough time to implement alternatives and notify the public should a systemic outage impact service. Should other restrictions (limited service) be considered in lieu of operating at restricted speed after the first 24 hours?</p></li></ul><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">We invite members to provide responses to these questions and any additional observations or comments which should be considered. <strong>Public comment period ends: December 27, 2024.</strong></p>
    </td>
  </tr>
</tbody></table>

</div>
<div id="line-line-section-9">

<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="transparent" class="line-section section-content">
  <tbody><tr>
    <td align="center" valign="middle" width="100%">
      <table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" class="line-section-table section-content" style="width:20%;min-width:20%;">
        <tbody><tr>
          <td align="center" valign="middle" class="section-content-cell" width="100%" style="padding-top:22px;padding-right:0;padding-bottom:22px;padding-left:0;">
            <div class="basic-line" data-line="solid" style="background:none;font-size:0;margin:0;line-height:0;height:0;width:100%;border-style:solid none;border-width:1px 0 0px;border-color:#000;">&nbsp;</div>
          </td>
        </tr>
      </tbody></table>
    </td>
  </tr>
</tbody></table>

</div>
<div id="text-text-section-10">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="transparent" class="text-section section-content">
  <tbody><tr>
    <td valign="top" class="section-text-area section-content-cell padding-mobile-both" style="padding-top:8px;padding-right:66px;padding-bottom:8px;padding-left:66px;color:#253551;background-color:transparent;">
      <h4 style="color:inherit;margin:1.414em 0 .5em;font-weight:400;line-height:1.25em;font-size:1.25em;mso-line-height-alt:1.25em;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;letter-spacing:.02em;text-align:center;"><strong>Track Geometry Measurement System (TGMS) Inspections [Docket # FRA–2024–0032]</strong></h4>
    </td>
  </tr>
</tbody></table>

</div>
<div id="text-text-section-11">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#FFFFFF" class="text-section section-content">
  <tbody><tr>
    <td valign="top" class="section-text-area section-content-cell" style="padding-top:19px;padding-right:11px;padding-bottom:11px;padding-left:11px;color:#253551;background-color:#fff;">
      <p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">On October 24th FRA published a proposed rule that would require commuter railroads who own mainline and controlled siding track to perform additional track inspections using a qualified Track Geometry Measurement System (TGMS). The new requirements would primarily modify § 213.236(a) (and corresponding requirements for Class 6 track) to require a qualified TGMS inspection a minimum of “three times within any 365-day period with not less than 90 days between inspections.” What defines a “qualified” TGMS system is further described in paragraphs (b) thru (d). Additional requirements including reporting and training are also outlined, along with requirements for TGMS inspection records (see § 213.241).</p><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">As noted at the CRC Fall Summit, this effort was originally part of an RSAC working group (Task 19-05), but the effort was abandoned before a consensus could be reached. Ostensibly, this rulemaking was based on conclusions from the various test programs that were performed under test waivers by BNSF, NS, CSX, CN, UP,  and CP. The rulemaking, however, is significantly deficient in its explanation of what lessons were learned from the test waiver programs, and how the results of testing performed under the waiver programs were incorporated. This information would have been valuable for comment at the NPRM stage, and wasn’t presented to the RSAC committee at large, so we’ll see if we can get this from the working group documents for any interested members who were not a part of those meetings.</p><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">In the NPRM FRA notes that “research indicates that all the track owners affected by this rulemaking are already performing TGMS inspections at or above the frequency that would be required by this NPRM. To determine if there is any value in commenting on this NPRM, CRC is seeking the following input from its member railroads:</p><ul data-rte-list="default" style="padding-left:25px;"><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">Are member railroads conducting testing with qualified TGMS equipment as noted by FRA in the NPRM (3 inspections a year / 90 days apart)?</p><ul data-rte-list="default" style="padding-left:25px;"><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">If not, what would be the estimated cost and implementation time required to implement such a program?</p></li></ul></li><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">Is the prohibition against performing visual inspections during TGMS runs, and specifically the phrase “sole responsibility” too restrictive (see § 213.236(h))?</p></li><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">Are there other revisions to track requirements under Part 213 that would be appropriate to be considered as part of an update to this part?</p></li></ul><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><strong>Public comment period ends: December 23, 2024.</strong></p>
    </td>
  </tr>
</tbody></table>

</div>
<div id="line-line-section-12">

<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="transparent" class="line-section section-content">
  <tbody><tr>
    <td align="center" valign="middle" width="100%">
      <table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" class="line-section-table section-content" style="width:20%;min-width:20%;">
        <tbody><tr>
          <td align="center" valign="middle" class="section-content-cell" width="100%" style="padding-top:22px;padding-right:0;padding-bottom:22px;padding-left:0;">
            <div class="basic-line" data-line="solid" style="background:none;font-size:0;margin:0;line-height:0;height:0;width:100%;border-style:solid none;border-width:1px 0 0px;border-color:#000;">&nbsp;</div>
          </td>
        </tr>
      </tbody></table>
    </td>
  </tr>
</tbody></table>

</div>
<div id="text-text-section-13">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#E0E0DB" class="text-section section-content">
  <tbody><tr>
    <td valign="top" class="section-text-area section-content-cell padding-mobile-both" style="padding-top:8px;padding-right:66px;padding-bottom:8px;padding-left:66px;color:#313131;background-color:#e0e0db;">
      <h4 style="color:inherit;margin:1.414em 0 .5em;font-weight:400;line-height:1.25em;font-size:1.25em;mso-line-height-alt:1.25em;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;letter-spacing:.02em;text-align:center;"><strong>Revisions to Part 211 – FRA Waiver Process and Requirements [Docket # FRA-2024-0033]</strong></h4>
    </td>
  </tr>
</tbody></table>

</div>
<div id="text-text-section-14">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#E0E0DB" class="text-section section-content">
  <tbody><tr>
    <td valign="top" class="section-text-area section-content-cell" style="padding-top:19px;padding-right:11px;padding-bottom:11px;padding-left:11px;color:#000;background-color:#e0e0db;">
      <p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">On October 9th, FRA published a proposed rule to amend its Rules of Practice as it relates to petitions for relief from certain safety regulations or requirements (i.e., waivers). These requirements have largely been unmodified since first adopted in 1976. The proposed rule would modify the procedures for waivers and safety-related proceedings by adding definitions to the statutory standards of “in the public interest” and “consistent with railroad safety” by which non-emergency safety waivers are required to be considered (49 U.S.C. 20103(d)(1)). The NPRM proposes to align the metric for railroad safety by establishing the current regulations as the “status quo” for which any petition must demonstrated equivalence or improvement over. The proposed rule defines “public interest” as alignment with “one or more of DOT’s priorities and innovation principals[.]” Additionally, the NPRM proposes to require any petition under Part 211 to demonstrate that a railroad has meaningfully consulted with “potentially impacted employees, and the local and general chairmen as well as the State and national legislative levels of any labor organizations that represent them.”</p><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">Unlike the recent PTC NPRM rulemaking in which FRA proactively engaged industry for input on its proposed modifications (and even to an extent the TGMS NPRM), it is unclear if FRA conducted any proactive engagement with industry stakeholders regarding these proposed changes to Part 211, making the comment period pivotal for incorporating perspectives of the impacted entities. Ironically, this NPRM is apparently following the practice its intending to allay, by relying solely on the public comment period rather than engaging with stakeholders for input prior to its development.</p><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">The NPRM notes that “[d]efining these terms will help clarify for petitioners and affected stakeholders how FRA will decide whether waiver requests meet the statutory standard.” While this stated intent is admirable, it’s unclear why the proposed definitions require incorporation into the regulations in lieu of formalized agency guidance. The proposed definitions simply appear to identify subjective categories of evaluation rather than performance-based criteria. Oddly, the preamble goes out of its way to note that a request for relief that “would reduce the number of inspections being performed” may not meet the proposed definition of “in the public interest.” This would appear to conflict with previous preamble guidance related to the proposal of alternative inspection intervals “when justified by accumulated, verifiable data”. Regardless, the statement is sufficiently vague to warrant clarifications. Likewise, the statement noting “[a] petition showing only that a proposal may improve the efficiency of railroad operations or reduce costs will likely not meet the standard in the proposed definition of ‘in the public interest’ …” also raises concern. Unlike most freight railroads, commuter railroads are not profit generating corporations, and their ability to be efficient with taxpayer dollars is inherently in the public’s interest. I’m sure this point is particularly paramount to our member railroads as we continue to struggle with rising maintenance and equipment costs, depressed ridership, and the never-ending rise in insurance costs.</p><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">Overall, the timing of this NPRM will undoubtedly make providing member input and timely industry comments a challenge, but the importance of the administrative procedures under Part 211 requires thoughtful consideration. We encourage members to review this NPRM and provide any feedback, concerns, or suggestions. Some questions to consider that would help CRC determine how to respond include:</p><ul data-rte-list="default" style="padding-left:25px;"><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">Are the proposed definitions and additional conditions appropriate for commuter rail agencies and the types of waivers anticipated?</p></li><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">Are the proposed definitions sufficiently clear and objective to comply with?</p></li><li style="font-weight:normal;margin-top:0px;margin-bottom:0px;margin-left:15px;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">Is the estimated cost to industry (~$1114 increased cost per waiver request) an accurate reflection of the potential burden?</p></li></ul><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><strong>Public comment period ends: December 30, 2024.</strong></p>
    </td>
  </tr>
</tbody></table>

</div>
<div id="line-line-section-15">

<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="transparent" class="line-section section-content">
  <tbody><tr>
    <td align="center" valign="middle" width="100%">
      <table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" class="line-section-table section-content" style="width:20%;min-width:20%;">
        <tbody><tr>
          <td align="center" valign="middle" class="section-content-cell" width="100%" style="padding-top:22px;padding-right:0;padding-bottom:22px;padding-left:0;">
            <div class="basic-line" data-line="solid" style="background:none;font-size:0;margin:0;line-height:0;height:0;width:100%;border-style:solid none;border-width:1px 0 1px;border-color:#000;">&nbsp;</div>
          </td>
        </tr>
      </tbody></table>
    </td>
  </tr>
</tbody></table>

</div>
<div id="text-text-section-16">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#FFFFFF" class="text-section section-content">
  <tbody><tr>
    <td valign="top" class="section-text-area section-content-cell" style="padding-top:19px;padding-right:11px;padding-bottom:11px;padding-left:11px;color:#253551;background-color:#fff;">
      <h4 style="color:inherit;margin:1.414em 0 .5em;font-weight:400;line-height:1.25em;font-size:1.25em;mso-line-height-alt:1.25em;margin-top:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;letter-spacing:.02em;text-align:center;"><strong>Railroad Safety Advisory Committee (RSAC)</strong></h4><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;">The 67th meeting of the RSAC was be held on October 9th, 2024, in Washington, DC. In addition to updates from the current active working groups, a review was provided of the current regulatory agenda and FRA rulemaking priorities. A more detailed briefing regarding these updates will be provided in next month’s regulatory update. Meeting documents, the agenda, presentation material will be posted on the RSAC <a href="https://rsac.fra.dot.gov/meetings?id=66" rel="nofollow" style="color:#064489 !important;">website</a>.</p><p class="" style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;"><em>There are no upcoming RSAC meetings currently scheduled.</em></p>
    </td>
  </tr>
</tbody></table>

</div>
<div id="spacer-spacer-section-17">

<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="transparent" class="spacer-section section-content">
  <tbody><tr>
    <td align="center" valign="middle" class="section-content-cell" height="22" style="height:22px;">
    </td>
  </tr>
</tbody></table>

</div>
<div id="text-text-section-18">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#098EB9" class="text-section section-content">
  <tbody><tr>
    <td valign="top" class="section-text-area section-content-cell padding-mobile-both" style="padding-top:11px;padding-right:66px;padding-bottom:22px;padding-left:66px;color:#fff;background-color:#098eb9;">
      <p style="color:inherit;font-size:1em;line-height:1.618em;margin:0 0 1.25em 0;font-weight:normal;margin-top:0;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;text-align:center;" class=""><strong>Follow</strong> us on <a href="https://www.linkedin.com/company/commuter-rail-coalition/" target="" rel="nofollow noopener noreferrer" style="color:#064489 !important;">LinkedIn</a> and <a href="https://twitter.com/RailCoalition" target="" rel="nofollow noopener noreferrer" style="color:#064489 !important;">Twitter</a>  </p>
    </td>
  </tr>
</tbody></table>

</div>
<div id="button-button-section-19">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#0A295F" class="button-section section-content" style="width:100%;background-color:#0a295f;">
  <tbody><tr>
    <td align="center" valign="middle" class="section-content-cell section-text-area" style="padding-top:9px;padding-right:22px;padding-bottom:8px;padding-left:22px;">
      
      <a href="https://www.commuterrailcoalition.org/home" class="button-section-box button-style-rounded" style="color:#064489 !important;display:inline-block;line-height:11px;margin:0;mso-padding-alt:0;text-align:center;text-decoration:none;transition:.15s;width:auto;background-color:#fff;border:1px solid #fff;border-radius:5.5px;padding:16px 0;"><i class="button-section-mso" style="letter-spacing:29.92px;mso-font-width:-100%;mso-text-raise:26.950000000000003px;">&nbsp;</i><span class="button-section-label" style="font-weight:inherit;line-height:inherit;margin:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;color:#064489;display:inline-block;font-size:11px;min-width:1px;mso-text-raise:15.95px;"><strong><span data-letter-spacing="3" style="font-size:inherit;font-weight:inherit;line-height:inherit;margin:0;letter-spacing:0.2em;">Join CRC</span></strong></span><i class="button-section-mso" style="letter-spacing:29.92px;mso-font-width:-100%;mso-text-raise:26.950000000000003px;">&nbsp;</i></a>
    </td>
  </tr>
</tbody></table>

</div>
                </td>
              </tr>
            </tbody></table>
            
              <table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" id="newsletter-section-footer">
                <tbody><tr>
                  <td align="center" valign="top" id="newsletter-section-footer-cell">
                    
<div id="footer-footer-section-stacked-top-0">



<table role="presentation" width="100%" cellpadding="0" cellspacing="0" border="0" bgcolor="#F6F6F6" class="footer-section footer-section-stacked section-content" style="background-color:#f6f6f6;">
  <tbody><tr>
    <td align="center" valign="top" class="section-text-area section-content-cell padding-mobile-both" style="padding-top:33px;padding-right:66px;padding-bottom:11px;padding-left:66px;">
      
  
  
    
      <a class="brand-logo-link" href="https://www.commuterrailcoalition.org/" style="color:#064489 !important;"><img class="brand-logo" src="https://images.squarespace-cdn.com/content/v1/64308e1bd95e74741ca4f52a/b6063f67-92c4-4fd0-8393-2aa0f1f20ae6/Commuter+Rail+Coalition_Bright+Blue.jpeg" height="22" alt="Commuter Rail Coalition" style="font-size:.8em;border:0;text-decoration:none;line-height:0;font-weight:normal;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;margin-bottom:13.75px;color:#444b50;display:inline;height:auto;max-height:22px;max-width:100%;width:auto;"></a>
    
  
  

      

      
      
  
    <p class="footer-company-info" style="line-height:1.618em;font-weight:normal;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;color:#444b50;font-size:11px;margin:0 0 13.75px 0;padding:0;">
  <a style="color:#444b50;text-decoration:none;font-size:inherit;font-family:inherit;font-weight:inherit;line-height:inherit;cursor:default;">Commuter Rail Coalition, 
  PO Box 235, 
  Alexandria, VA 22313, 
  United States</a>
</p>
  

      
<p class="footer-links" style="line-height:1.618em;font-weight:normal;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:11px;color:#313131;margin:0 0 13.75px 0;padding:0;">
  Powered by <a href="https://www.squarespace.com?channel=product_refer&amp;subchannel=customer&amp;source=email_campaigns_button&amp;campaign=64308e1bd95e74741ca4f52a&amp;utm_medium=product_refer&amp;utm_source=email_campaigns_button" class="sqsp-link" style="color:#313131;text-decoration:underline;display:inline-block;">Squarespace</a>
</p>


      <p class="footer-links" style="line-height:1.618em;font-weight:normal;margin-bottom:0;font-family:'DejaVu Sans Condensed', 'Liberation Sans', 'Nimbus Sans L', 'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:11px;color:#313131;margin:0 0 13.75px 0;padding:0;">
  <a href="#" class="unsubscribe-link" style="color:#313131;text-decoration:underline;">
    <span class="unsubscribe-link-text" style="font-size:inherit;font-weight:inherit;line-height:inherit;margin:0;">Unsubscribe</span>
  </a>
</p>

    </td>
  </tr>
</tbody></table>

</div>
                  </td>
                </tr>
              </tbody></table>
            
          </td>
        </tr>
      </tbody></table>
    </td>
  </tr>
</tbody></table>

  
</body></html>
