{"id":552930,"date":"2018-11-26T10:44:28","date_gmt":"2018-11-26T14:44:28","guid":{"rendered":"https:\/\/ntrs.nasa.gov\/search.jsp?R=20180007529"},"modified":"2018-11-26T10:44:28","modified_gmt":"2018-11-26T14:44:28","slug":"evolution-of-electronic-approval-request-procedures-at-charlotte-douglas-international-airport-2","status":"publish","type":"post","link":"https:\/\/spaceweekly.com\/?p=552930","title":{"rendered":"Evolution of Electronic Approval Request Procedures at Charlotte Douglas International Airport"},"content":{"rendered":"<p>Abstract: A departure approval request, or APREQ, establishes a later runway departure time for a flight, allowing it to absorb tactical delay on the ground. APREQ times are traditionally coordinated by a process known as &#8220;call-for-release&#8221; whereby an airport surface traffic manager calls an airspace traffic manager on the telephone. This research examines new electronic APREQ coordination enabled by the NASA Airspace Technology Demonstration-2 system and compares it to the traditional call-for-release&#8230;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Abstract: A departure approval request, or APREQ, establishes a later runway departure time for a flight, allowing it to absorb tactical delay on the ground. APREQ times are traditionally coordinated by a process known as &#8220;call-for-release&#8221; whereby an &#8230;<\/p>\n","protected":false},"author":60,"featured_media":615444,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-552930","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry"],"_links":{"self":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/552930","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/users\/60"}],"replies":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=552930"}],"version-history":[{"count":1,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/552930\/revisions"}],"predecessor-version":[{"id":552931,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/posts\/552930\/revisions\/552931"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=\/wp\/v2\/media\/615444"}],"wp:attachment":[{"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=552930"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=552930"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/spaceweekly.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=552930"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}