FLYHT is committed to deliver products & services that meet or exceed the requirements and expectations of our customers, add value to FLYHT and our customers, and comply with applicable regulatory requirements.
FLYHT strives to continually improve its quality management system through the establishment of quality objectives and leveraging innovative suggestions from employees.
FLYHT Aerospace Solutions Ltd. holds certificates from:
FLYHT holds AS9100 certification.
FLYHT also holds multiple Supplemental Type Certificates (STCs) to make appropriate modifications, such as installing Automated Flight Information Reporting System (AFIRS™) technology, to an aircraft’s approved design.
FLYHT has received STC approvals from Transport Canada Civil Aviation (TCCA), the United States Federal Aviation Administration (FAA), the European Aviation Safety Agency (EASA), the General Administration of Civil Aviation of China (CAAC), the National Civil Aviation Agency (ANAC) in Brazil and the Direccion General de Aeronautica Civil (DGAC) in Mexico for various aircraft models depending on customer requirements. FLYHT is currently pursuing STC validations from the State Aviation Authority of Ukraine (SAAU) and the Hong Kong Civil Aviation Department (HKCAD).
FLYHT’s expertise in airworthiness certification enabled us, in October 2008, to join a select group of Canadian companies who are approved by TCCA as a DAO. Very few organizations achieve DAO status because of the time and expertise required to meet TCCA standards. FLYHT’s DAO status, along with the delegations it has received, allows the Company to obtain and revise its own STCs with minimal TCCA oversight. This speeds up the process by lessening wait times, and reduces cost and reliance on contractors.
As a component of its DAO status, the Company employs the services of a delegated engineer, allowing for the approval of changes and the systems and electrical design aspects of an airworthiness certification. If an issue is encountered during the STC process, the delegate has the authority to approve necessary changes and continue the process without the involvement of an external party.
The process to receive an STC takes some time, but in all cases it starts with an STC application through the TCCA, FAA or EASA.
FLYHT typically starts the process with TCCA by opening an application with the regulator before an STC package is created. The data package is prepared, including engineering documents outlining how AFIRS equipment is substantiated and installed on the aircraft, and the package is submitted to TCCA for approval.
Once approved, first-of-type ground and flight testing takes place to fulfill regulatory requirements. FLYHT requires access to the proposed types and models of aircraft, which is done in cooperation with an existing or potential customer.
After all tests are complete, FLYHT submits an application for the activation and data package to TCCA confirming all regulatory requirements have been met and the AFIRS unit is fit for operation on that aircraft type as designed. From there, TCCA approves the submission and an STC is issued.
To acquire an STC from a different national regulator, FLYHT submits an application through TCCA to a regulator such as the FAA or EASA with the STC data package previously approved by TCCA. The regulator then reviews the package and issues an STC for that country based on their validation of the TCCA STC.
Timelines required for the TCCA approval process will vary depending on aircraft and workloads, but typically take about three to four months, with an additional three to eight months if an STC is required from another regulator like the FAA or EASA.
TCCA | FAA | EASA | CAAC | ANAC | ||||||
---|---|---|---|---|---|---|---|---|---|---|
220 | 228 | 220 | 228 | 220 | 228 | 220 | 228 | 220 | 228 | |
A | A | A | A | A | A | A | A | Airbus A319, A320, A321 | ||
P | Airbus A300 | |||||||||
A | A | A | ATR42-300 | |||||||
A | ATR42-500 | |||||||||
A | A | A | ATR72 -100, -200 | |||||||
A* | ATR42-500 “600 Version” *STC Twenty One | |||||||||
A* | ATR72-212A “600 Version” *STC Twenty One | |||||||||
A | A | A | A | Boeing B737 -200 | ||||||
A | A | A | A | A | A | A | A | A | Boeing B737 -300, -400, -500 | |
A | I | A | A | A | Boeing B737 -600 | |||||
A | A | A | A | A | A | A | A | A | Boeing B737 -700, -800 | |
A | Boeing B737 -900ER | |||||||||
A | Boeing 747 -200 | |||||||||
A | A | A | A | A | A | A | A | Boeing 757 -200 | ||
A | A | A | A | A | A | A | A | Boeing 767 -200, -300 | ||
A | A | Boeing B777 | ||||||||
A | A* | A | A* | A | A* | Bombardier DHC 8 -100, -200, -300 *Avmax | ||||
A | A | A | Bombardier DHC 8 -400 | |||||||
A | A | A | A | A | A | A | Bombardier CRJ 100, 200, 440 | |||
A | A | A | A | Bombardier CRJ -700, 900 | ||||||
A | A | McDonnell Douglas DC-10 (KC-10 military) | ||||||||
A | McDonnell Douglas MD-82 | |||||||||
A | A | McDonnell Douglas MD-83 | ||||||||
A | Fokker 100 | |||||||||
A | A | A | A | A | A | Hawker Beechcraft -750, 800XP, 850XP, 900XP | ||||
A | Viking Air DHC -7 (LSTC) | |||||||||
A | A | A | A | Embraer EMB 190 | ||||||
A | Embraer Legacy 600 and EMB – 135/145 |
AFIRS™ 220 or 228 model
FLYHT has also received an approved AFIRS 228 STC for the Bombardier CRJ- 700, -900, B737-300, -400, -500 and B737-700, -800 from the Direccion General de Aeronautica Civil (DGAC) in Mexico.
FLYHT has AFIRS 228 applications in progress with the State Aviation Administration of Ukraine (SAAU) for B737-300, -400, -500, B737-700, -800 and B767 aircraft. An AFIRS 228 application is also in progress with the Hong Kong Civil Aviation Department (HKCAD) for the Airbus A319, A320 and A321.
#500, 1212 – 31 Avenue NE
Calgary, Alberta, Canada T2E 7S8
Telephone: 1-403-250-9956
Email: info@flyht.com
FLYHT Inc.
4600 South Syracuse, Suite 900
Denver, CO, USA 80237-2719
Europe Office
CrossConsense GmbH & Co KG
Hanauer Landstraße 312
D-60314, Frankfurt, Germany
Tel.: +49 (0) 69.40 35 76 00
2021 FLYHT Aerospace Solutions Ltd.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |