曝光台 注意防骗
网曝天猫店富美金盛家居专营店坑蒙拐骗欺诈消费者
FDA software vendor in consultation with the operator/manufacturer) establishes the main areas of interest
to operators.
Examples: High lift-off rotation rate, stall warning, GPWS warning, flap limit speed exceedence, fast
approach, high/low on glide slope, and heavy landing.
16.3.14 FDA provides useful information which can complement that provided in crew reports.
Examples: Reduced flap landing, emergency descent, engine failure, rejected take-off, go-around,
TCAS or GPWS warning, and system malfunctions.
16.3.15 Companies may also modify the standard set of core events (in accordance with the
agreement with their pilots) to account for unique situations they regularly experience, or the SOPs they use.
Example: To avoid nuisance reports from a non-standard SID.
16-6 Safety Management Manual (SMM)
16.3.16 They may also define new events (with the agreement of the pilots) to address specific
problem areas.
Example: Restrictions on the use of certain flap settings to increase component life.
16.3.17 Care must be taken that, in order to avoid an exceedence, flight crew do not attempt to fly the
FDA profile rather than follow SOPs. Such an action can quickly turn a poor situation into something worse.
Routine measurements
16.3.18 Increasingly, data are retained from all flights, not just the ones producing significant events. A
selection of parameters is retained that is sufficient to characterize each flight and allow a comparative
analysis of a wide range of operational variability. Trends may be identified before there are statistically
significant numbers of events. Emerging trends and tendencies are monitored before the trigger levels
associated with exceedences are reached.
Examples of parameters monitored: take-off weight; flap setting; temperature; rotation and lift-off
speeds versus scheduled speeds; maximum pitch rate and attitude during rotation; and gear retraction
speeds, heights and times.
Examples of comparative analyses: pitch rates from high versus low take-off weights; good versus bad
weather approaches; and touchdowns on short versus long runways.
Incident investigation
16.3.19 Recorded data provide valuable information for follow-up to mandatory reportable incidents
and other technical reports. Quantifiable recorded data have been useful in adding to the impressions and
information recalled by the flight crew. The recorded data also provide an accurate indication of system
status and performance, which may help in determining cause and effect relationships.
Examples of incidents where recorded data could be useful:
a) emergencies, such as:
1) high-speed rejected take-offs;
2) flight control problems; and
3) system failures;
b) high cockpit workload conditions as corroborated by such indicators as:
1) late descent;
2) late localizer and/or glide slope interception;
3) large heading change below a specific height; and
4) late landing configuration;
c) unstabilized and rushed approaches, glide path excursions, etc.;
d) exceedences of prescribed operating limitations (such as flap limit speeds, engine overtemperatures,
Vspeeds, and stall onset conditions; and
Chapter 16. Aircraft Operations 16-7
e) wake vortex encounters, low-level wind shear, turbulence encounters or other vertical
accelerations.
Continuing airworthiness
16.3.20 Both routine and event data can be utilized to assist the continuing airworthiness function. For
example, engine-monitoring programmes look at measures of engine performance to determine operating
efficiency and predict impending failures.
Examples of continuing airworthiness uses: engine thrust level and airframe drag measurements;
avionics and other system performance monitoring; flying control performance; and brake and landing
gear usage.
Integrated safety analysis
16.3.21 All the data gathered in an FDA programme should be kept in a central safety database. By
linking the FDA database to other safety databases (such as incident reporting systems and technical fault
reporting systems), a more complete understanding of events becomes possible through cross-referencing
the various sources of information. Care must be taken, however, to safeguard the confidentiality of FDA
data when linking the data to identified data.
Example of integration: A heavy landing results in a crew report, an FDA event and an engineering
report. The crew report provides the context, the FDA event provides the quantitative description, and
the engineering report provides the result.
16.3.22 The integration of all available sources of safety data provides the operator’s SMS with viable
information on the overall safety health of the operation.
FDA equipment
中国航空网 www.aero.cn
航空翻译 www.aviation.cn
本文链接地址：
Safety Management Manual (SMM) 安全管理手册(111)
