|

Air Worthiness Directive Issued May 14

Similar Posts

  • | |

    Dassault Reaches Milestone With 100th Falcon 7X Delivery

    LITTLE ROCK, Arkansas, — Dassault yesterday delivered the 100th Falcon 7X during a ceremony at its completion center in Little Rock, Arkansas. The aircraft was delivered to a Brazilian financial services company.

    “We promised to design and build the most technically advanced and best flying aircraft in the industry and we’ve already achieved that 100 times,” said John Rosanvallon, President and CEO of Dassault Falcon. “During that time, feedback from pilots and passengers alike has been very positive. Pilots said they appreciate, in particular, the digital flight control system which makes the Falcon 7X so responsive and easy to maneuver. The superb cabin environment is praised by passengers for its smooth flying comfort and quietness.

    To date, the 5,950 nm Falcon 7X fleet has accumulated more than 57,000 flight hours, operating in over 25 countries with orders coming from more than 40 countries. The fleet leader has logged more than 3,000 flight hours since its delivery mid 2007. “The high usage rate (higher than other Falcons) demonstrates that the Falcon 7X is a very active part of many flight departments,” said Jacques Chauvet, Senior Vice President of Customer Service. “Its versatility helps account for its popularity and having gathered over 200 orders”.

    The Falcon 7X has received type certification from 16 aviation authorities and is the only long range business jet with EASA and FAA approvals to use the challenging London City airport.

    7X Background
    The Falcon 7X has the longest range of any Falcon business jet and is the most fuel efficient jet in its class. Since its entry into service in 2007, the 7X cabin has set a new standard for business jets. The cabin has 28 windows which are 10% bigger than previous Falcons. It also features a low in flight cabin altitude of 6,000 feet, even while cruising at an altitude of 51,000 ft, and an advanced temperature control system that maintains the environment to within one degree throughout the entire cabin. Internal sound level has been reduced to 52 dB which is the result of breakthroughs in design, materials and cushioned engine mounts.

    First announced at the Paris Air Show in 2001, the Falcon 7X is the first business jet with a digital flight control system and was simultaneously certified by both the EASA and the FAA on April 27, 2007. It features the award-winning EASy Flight Deck and is powered by three Pratt & Whitney Canada PW307A engines. Its 5,950 nm range (eight passengers, M.80 with NBAA IFR reserves) can comfortably connect 95% of the commonly used business aviation city pairs.

    About Dassault Falcon
    Dassault Falcon is responsible for selling and supporting Falcon business jets throughout the world. It is part of Dassault Aviation, a leading aerospace company with a presence in over 70 countries across five continents. Dassault Aviation produces the Rafale fighter jet as well as the complete line of Falcon business jets. The company has assembly and production plants in both France and the United States and service facilities on multiple continents. It employs a total workforce of over 12,000. Since the rollout of the first Falcon 20 in 1963, 2,000 Falcon jets have been delivered to 67 countries worldwide. The family of Falcon jets currently in production includes the tri-jets-the Falcon 900DX, 900LX, and the 7X-as well as the twin-engine 2000LX.

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • |

    Press Release – FAA Accepts Final FTI Outage Review Panel Report


    For Immediate Release
    November 12, 2010

    The Federal Aviation Administration (FAA) today accepted the second and final report on the November 2009 telecommunications outage prepared by an independent review panel assigned to investigate the incident.

    FAA Administrator Randy Babbitt had asked the panel to examine the cause of the FAA Telecommunications Infrastructure (FTI) outage and to recommend strategies to reduce the potential for similar future outages. He also asked the panel to examine the FTI’s present and future architecture as it relates to emerging technology and future FAA systems.

    The FTI system operates 24 hours a day seven days a week and provides communication support for the National Airspace System. Harris Corporation operates and maintains the FTI for the FAA.

    Last April the FAA began carrying out the panel’s initial recommendations which included:

    • Developing new automated tools for making configuration changes to network devices
    • Increasing FTI workforce staffing during network maintenance
    • Developing an alternate means for the entry of flight plan information to limit the impact of telecommunications network failures on the flight plan entry system.
    • Creating two network enterprise management centers which give the FAA greater situational awareness of network activity and maintenance
    • Installing additional cybersecurity measures throughout the National Airspace System

    The final report on the FTI outage lays out 14 long-term strategic recommendations the FAA should pursue as it transitions to future network systems. The FAA has already begun evaluating and working through the recommendations which revolve around five areas:

    • Governance: the decision making process for FAA systems
    • Situational Awareness: FAA network monitoring and information sharing
    • Interoperability: data sharing between systems and stakeholders
    • Resilience: ability of a network to continue operating under a variety of conditions
    • Cyber Security: the ability to thwart, detect, and respond to any attempts to compromise the system.

    On the morning of Nov. 19, 2009 the FTI experienced an outage that resulted in system-wide delays. During the four-hour event, air traffic controllers managed flight plan data manually and safely according to FAA contingency plans. Air traffic control radar and communication were not affected during that time and critical safety systems remained up and running.

    The panel confirmed the FAA’s preliminary assessment that the November outage was caused by a series of errors in network maintenance and monitoring during a telecommunications upgrade.

    The panel is made up of the following participants: FAA Chief Information Officer David Bowen; Assistant to the President and U.S. Chief Technology Officer Aneesh Chopra; Department of Transportation Chief Information Officer Nitin Pradhan; Noblis CEO Amr Elsawy; former Director of Command, Control, Communications, and Computer Systems Vice Admiral (Ret) Nancy Brown; FAA Air Traffic Organization (ATO) CIO Steve Cooper; and FAA Assistant Chief Counsel for Acquisition and Commercial Law Patricia McNall.

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • | | | | |

    Update to “Cold Temperature Restricted Airports” list


    Subject: Update to “Cold Temperature Restricted Airports” list located in Notice to Airmen Publication (NTAP) Graphic Notices. www/faa.gov/air_traffic/publications/notices.

    Purpose: This publication provides operators with information related to cold temperature altitude restrictions. It contains the addition and subtraction of airports to the Cold Temperature Restricted Airports list located in the NTAP.

    Background: In response to recognized safety concerns over cold weather altimetry errors, the Federal Aviation Administration (FAA) completed a risk analysis to determine if current Title 14 of the Code of Federal Regulations (14 CFR) Part 97 instrument approach procedures in the United States National Airspace System (NAS) are at risk during cold temperature operations. From this study the FAA published an NTAP providing pilots a list of airports, the affected segments and procedures needed to correct published altitudes at the restricted temperatures.

    Discussion: Pilots may correct all altitudes from the initial approach fix (IAF) through the missed approach (MA) final holding altitude (All Segments Method). There will be a single temperature in Celsius (C) next to the snowflake ICON to indicate when this procedure will be required. Pilots wishing to use the All Segments Method and familiar with the NTAP procedure for applying a correction are not required to review the NTAP airport list for affected segments. Pilots wishing to continue correcting segment by segment must review the NTAP airports list for segment(s) affected (NTAP Segment(s) Method). The front matter in the FAA U.S Terminal Procedures Publication will also provide this information.

    Added Airports

    Idaho: Driggs-Reed Memorial (KDIJ) (-31C)

    Maine: Greenville Muni (3B1) (-29C)

    New Hampshire: Laconia Muni (KLCI) (-25C), Parlin Field (2B3) (-24C)

    Pennsylvania: Washington County (KAFJ) (-27C)

    South Dakota: Pine Ridge (KIEN) (-33C)

    Washington: Richland (KRLD) (-19C)

    Deleted Airports

    Alaska: Perryville (PAPE), Togiak (PATG), Willow (PAUO), White Mountain (PAWM)

    Colorado: Spanish Peaks Airfield (4V1), McElroy Airfield (20V), Walden-Jackson County (33V)

    Maine: Eastern Slopes Rgnl (KIZG)

    Maryland: Greater Cumberland Rgnl (KCBE)

    Massachusetts: Walter J. Koladza (KGBR)

    Minnesota: St Paul Downtown Holman Fld (KSTP), Tower Municipal (12D)

    Montana: Cut Bank Intl (KCTB), Deer Lodge City County (38S)

    Nevada: Carson (KCXP), Minden-Tahoe (KMEV)

    New Hampshire: Dillant-Hopkins (KEEN)

    New Mexico: Taos Rgnl (KSKX)

    New York: Dansville (KDSV), Massena Intl-Richards Field (KMSS), Hamilton Muni (KVGC), Cortland County-Chase Field (N03), Randall (06N), Schenectady County (KSCH)

    North Dakota: Watford City Muni (S25)

    Oregon: Astoria Rgnl (KAST)

    Pennsylvania: Seamans Field (9N3)

    The current T-XX°C/XX°F icon will be changed to T-XX°C.

    This change will be done incrementally on airport approach plates. The icon indicates a cold temperature altitude correction will be required on an approach when the reported temperature is, “at or below” the temperature specified for that airport. During this process, pilots may see temperatures on the current approach plates that are different than the temperature listed in the NTAP. The NTAP temperature is the updated temperature. Pilots may use the temperature published in the current TPP to make corrections if warmer than the NTAP listed temperature.

    Pilots must understand they will be responsible for applying altitude corrections and must advise Air Traffic Control (ATC) when these corrections are to be made on any segment other than the final segment. Air Traffic Control is not responsible for making any altitude corrections and/or advising pilots that an altitude correction is required at a restricted airport.

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • |

    FAA Controllers to Use New Terminology Prior to Takeoff

    August 31 — Pilots authorized by air traffic controllers to taxi onto runways and await takeoff clearance will be instructed to “line up and wait” rather than “position and hold” beginning on September 30 under new terminology adopted by the Federal Aviation Administration. The new terminology, which was recommended by the National Transportation Safety Board, conforms to terminology used internationally under International Civil Aviation Organization guidelines.

    A safety analysis conducted by the FAA’s Air Traffic Organization Terminal Services determined that adopting the phrase “line up and wait” will eliminate confusion, particularly among pilots who also fly overseas, and further reduce the risk of runway incursions.
    Beginning September 30, controllers will state the aircraft’s call sign, state the departure runway and then instruct pilots to “line up and wait,” i.e., “United 451, Runway 33L, line up and wait.” The phrase, “traffic holding in position” will continue to be used to advise other aircraft that traffic has been authorized to line up and wait on an active runway.

    The FAA will continue to emphasize that pilots are not permitted to cross any runway encountered while taxiing without explicit instructions from controllers.

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • |

    PR: FAA Proposes $185,750 Civil Penalty Against Kingfisher Air

    ATLANTA – The Federal Aviation Administration (FAA) is proposing a civil penalty of $185,750 against Kingfisher Air Services Air Safari, Inc., of San Juan, P.R., for allegedly operating a Cessna 208B on 44 flights between June 2 and June 11, 2010, when it was not in compliance with Federal Aviation Regulations.

    The FAA alleges that three pilots reported that the aircraft’s engine temperature exceeded the take-off limits before the carrier took the required maintenance action and had the engine repaired. The engine maintenance manual requires the operator to send the engine to an overhaul facility for a light overhaul when such problems are reported. The carrier failed to send the engine for overhaul after the first and second pilot reports.

    To include the featured image in your Twitter Card, please tap or click their icon a second time.
  • |

    FAA Orders Inspections of Honeywell Emergency Locator Transmitters


    The FAA is issuing an Airworthiness Directive (AD) identical to the August 26 Transport Canada Civil Aviation (TCCA) directive which requires airlines to inspect Honeywell emergency locator transmitters (ELTs) by January 14, 2014 to prevent an electrical short and possible ignition source. The FAA AD has the same deadline for the U.S. fleet and will impact approximately 4,000 airplanes at a total cost of approximately $325,720. The investigation of the July 12, 2013 Ethiopian Airlines Boeing 787 fire at Heathrow Airport continues under the leadership of the United Kingdom Air Accident Investigation Branch (AAIB).

    In George’s Point of View

    Good for Transport Canada Civil Aviation beating us to the punch. Too bad that the deadline is January 14, 2014. Seems like they could behave with a bit more urgency with a potential fire hazard. Does this mean that–if one of these Honeywell emergency locator transmitters happens to cause a fire between now and January 14, 2014, the TCCA and the FAA are responsible? By setting a date months away, aren’t these agencies downplaying the hazard potential?

    To include the featured image in your Twitter Card, please tap or click their icon a second time.