Nearly 25 years separate the accident involving LAPA Flight 3142 in Argentina from the crash of Voepass Flight 2283 in Brazil. During that period, commercial aviation advanced significantly in aircraft technology, crew training, safety management, data monitoring and regulatory oversight.
Yet both accidents reveal a disturbing reality: technology and regulations cannot prevent an accident when warnings are underestimated, procedures lose their authority and organizational defenses are gradually weakened.
The two events were technically very different. LAPA 3142 involved a Boeing 737-200 attempting to take off without its flaps properly configured. Voepass 2283 involved an ATR 72 operating in severe icing conditions while experiencing problems with its airframe de-icing system.
The similarity is not in the aircraft or the immediate technical mechanism. It is found in the progressive failure of the barriers that should have stopped each accident sequence.
LAPA Flight 3142: a takeoff without flaps
On August 31, 1999, LAPA Flight 3142 was scheduled to operate from Buenos Aires to Córdoba. The aircraft was a Boeing 737-204C, registration LV-WRZ.
During the preparation for departure, the flight crew failed to extend the flaps to the required takeoff position. When takeoff thrust was applied, the Takeoff Warning System — TOWS — generated an aural warning indicating that the aircraft was not correctly configured.
The crew continued the takeoff.
Without the flaps in the planned position, the aircraft could not achieve the expected takeoff performance. The official investigation conducted by Argentina’s Junta de Investigaciones de Accidentes de Aviación Civil — JIAAC — identified the failure to extend the flaps and the crew’s disregard of the configuration warning as the immediate cause of the accident. The event resulted in 65 fatalities, including two people on the ground. JIAAC final report.
The investigation also found that non-operational conversations had been mixed with checklist execution. It described poor cockpit discipline, distraction and the loss of a sterile cockpit environment during a critical phase of flight.
Voepass Flight 2283: icing, degraded performance and loss of control
On August 9, 2024, Voepass Flight 2283 was operating from Cascavel to São Paulo–Guarulhos. The aircraft was an ATR 72-500, registration PS-VPB.
The aircraft encountered atmospheric conditions favorable to severe icing while cruising at Flight Level 170, approximately 17,000 feet. According to Brazil’s Center for Investigation and Prevention of Aeronautical Accidents — CENIPA — the aircraft had experienced problems with its Airframe De-Icing system.
The flight crew received multiple warnings related to low speed and degraded aircraft performance. The required procedures were not adequately carried out, performance continued to deteriorate and the aircraft eventually stalled and entered an unrecoverable loss-of-control sequence.
All 62 occupants were killed.
CENIPA’s final report identified contributing factors involving aircraft maintenance, weather, flight planning, decision-making, cockpit coordination, organizational processes, management supervision, safety culture and the actions of Brazil’s civil aviation regulator, ANAC. CENIPA English-language final report.
Different technical failures, similar organizational patterns
It would be technically incorrect to compare a flap configuration error with an icing-related loss of performance as if they were the same event.
They were not.
The meaningful comparison begins when we examine how each safety system responded before the aircraft reached an irreversible condition.
In both cases:
- relevant warning systems operated;
- established procedures were available;
- trained and licensed crews were in control;
- information existed before the final loss of safety margins;
- organizational oversight should have detected important risks;
- the expected response did not occur;
- successive barriers failed to stop the accident sequence.
This is why describing either event only as “pilot error” produces an incomplete safety analysis.
The aircraft warned the crews
On LAPA 3142, the takeoff configuration warning sounded when thrust was applied. The crew had an opportunity to reject the takeoff, identify the configuration problem and return to the checklist.
On Voepass 2283, the crew received repeated Aircraft Performance Monitoring — APM — warnings related to low speed and degraded performance. CENIPA concluded that the corresponding procedures were not properly followed.
In both events, the aircraft provided information that something was wrong.
Warning systems, however, do not protect an aircraft independently. A warning must be recognized, understood and connected to a trained response.
If recurring alerts are routinely experienced without serious consequences, crews may gradually become less sensitive to them. What was initially recognized as abnormal can begin to feel familiar. Familiarity can then be mistaken for safety.
Procedures existed but no longer controlled the operation
LAPA’s crew had checklists and rejected-takeoff procedures. The checklist was nevertheless conducted amid personal conversations and divided attention. The flap item was not properly completed, and the warning did not produce an immediate rejected takeoff.
Voepass also had procedures for an Airframe De-Icing system fault and for warnings generated by the APM. According to the final report, the applicable Quick Reference Handbook — QRH — procedures were not adequately carried out.
This reveals a common gap between formal compliance and operational reality.
An airline may have complete manuals, approved procedures and current training records while daily operations gradually move away from those standards.
When that happens, the organization described in official documents is no longer the same organization operating the aircraft.
Informality can weaken formal safety defenses
The LAPA cockpit voice recorder revealed personal conversations during preparation, engine start and taxi. Those conversations interfered with checklist discipline and concentration.
In the Voepass investigation, CENIPA described a broader culture of informality affecting different levels and departments. According to the report, this environment created opportunities for improvisation, permissiveness and the relaxation of safety rules.
Informality is not automatically unsafe. Good professional relationships can improve communication and cooperation.
The risk appears when informal practices replace formal safety processes.
A mechanical problem mentioned verbally is not equivalent to a properly documented technical discrepancy. An informal understanding between pilots and maintenance personnel cannot replace an aircraft logbook entry. A friendly organizational environment cannot justify bypassing the Minimum Equipment List — MEL — or an approved operating procedure.
Aviation requires trust, but it also requires traceability.
Critical information existed before both flights
The LAPA investigation reviewed the captain’s professional history and identified previous observations involving cockpit coordination, maneuver configuration, memory items and responses to critical situations.
Those warning signs did not produce a sufficiently effective organizational intervention before Flight 3142.
In the Voepass case, problems involving the Airframe De-Icing system had reportedly appeared on previous flights but were not formally entered in the Technical Logbook. Without that record, the operator lost the opportunity to apply preventive measures such as corrective maintenance, dispatch under MEL restrictions, aircraft substitution or route replanning.
In both cases, safety-relevant information existed before the accident flight.
The central failure was not simply the absence of information. It was the organization’s inability to collect, connect, evaluate and convert that information into preventive action.
Information that does not move through the proper channels cannot function as a safety barrier.
The normalization of deviation
CENIPA’s Voepass report explicitly addressed the normalization of deviations. Repeated warnings and irregular practices that had not previously produced an accident contributed to complacency and reduced risk perception.
The LAPA report did not use that modern safety-management concept in exactly the same way. Nevertheless, the documented repetition of performance concerns, procedural indiscipline and ineffective follow-up supports a similar analytical question: had abnormal behavior gradually become tolerated because earlier occurrences had not resulted in disaster?
Normalization typically develops through a predictable sequence:
- A rule is bypassed under exceptional circumstances.
- Nothing serious happens.
- The shortcut is repeated.
- The deviation becomes familiar.
- Familiarity reduces concern.
- The exception becomes an informal operating standard.
The absence of a previous accident does not prove that the practice was safe. It only means that the remaining defenses had continued to compensate for the deviation.
Until they no longer could.
CRM training did not guarantee effective coordination
LAPA conducted Crew Resource Management — CRM — training. Yet Flight 3142 displayed many of the problems CRM is intended to prevent: distraction, inadequate communication, weak cross-checking and failure to respond collectively to a critical warning.
In the Voepass case, CENIPA identified inadequate task management, communication problems and ineffective cockpit coordination as performance progressively deteriorated.
A completed CRM course does not necessarily mean CRM principles are present in daily operations.
The real test appears in the cockpit:
- whether tasks are clearly divided;
- whether the monitoring pilot remains effective;
- whether a first officer can challenge an unsafe decision;
- whether the captain remains open to contrary information;
- whether abnormal indications are discussed accurately;
- whether either pilot can stop an unsafe operation.
Training records measure attendance and qualification. Organizational behavior determines whether that training has real authority.
Management supervision failed to stop the drift
In the LAPA case, previous evaluations contained repeated concerns, yet the organization’s follow-up did not prevent similar weaknesses from appearing during the accident flight. The report also identified gaps in training and inspection records.
In the Voepass investigation, ineffective management supervision was classified as a contributing factor. Informal practices in both flight operations and maintenance created conditions in which deviations became increasingly accepted.
Effective supervision is more than verifying paperwork. It must determine how the operation is actually being conducted.
Management should be able to answer:
- Are crews following procedures outside the simulator?
- Are maintenance discrepancies being formally recorded?
- Are recurring warnings being investigated?
- Is the MEL being properly applied?
- Are training deficiencies being corrected and rechecked?
- Are operational, maintenance and safety departments sharing information?
- Can employees report a risk without pressure to keep the aircraft flying?
A company may appear compliant during a document review while its daily safety margins continue to deteriorate.
Technology cannot compensate for a weak safety culture
Between 1999 and 2024, aircraft systems became more capable, flight data monitoring expanded and Safety Management Systems became central to airline operations.
Yet technology only provides information and additional defenses. It cannot force an organization to respect a warning, document a discrepancy or stop an unsafe operation.
Regulations face a similar limitation.
A regulation can define the required standard. It cannot guarantee that the standard remains influential during daily operational decisions. That depends on supervision, accountability, reporting culture and management priorities.
Both accidents demonstrate that safety is not measured by the number of manuals, software systems or training certificates an airline possesses. It is measured by what happens when continuing the flight becomes easier than stopping it.
An important difference in regulatory oversight
The two reports did not reach the same conclusion regarding government oversight.
In the Voepass investigation, CENIPA classified ANAC’s actions as a contributing factor. Previous inspections had identified technical and procedural nonconformities, but the measures adopted were considered insufficient to prevent unsafe practices from continuing.
In the LAPA report, JIAAC stated that the regulations and procedures established by both the operator and the state oversight system would have been sufficient to prevent the accident if they had been followed.
It would therefore be inaccurate to claim that the aviation authorities played an identical role in both cases.
The valid comparison lies in the organizational and operational barriers: procedures existed, warning systems operated and relevant information was available, yet the system did not convert those defenses into timely action.
The lasting lesson from LAPA and Voepass
Twenty-five years, new technology and more extensive regulation were not enough to eliminate similar patterns of procedural drift.
The accidents show how safety can deteriorate when:
- warnings become routine;
- procedures lose operational authority;
- discrepancies are not formally recorded;
- known performance concerns are not effectively addressed;
- CRM exists in training but not in cockpit behavior;
- informal practices replace traceable decisions;
- supervision verifies documents without understanding daily operations.
The final error may occur in the cockpit, but the conditions that make it possible are often created much earlier.
LAPA 3142 and Voepass 2283 remind us that aviation safety cannot be preserved by technology and regulation alone. It depends on an organization’s willingness to detect weak signals, document uncomfortable facts and stop an operation before the remaining barriers are exhausted.
The aircraft involved in both accidents issued warnings. The deeper question is whether their organizations had already stopped listening.
By Marcuss Silva Reis
Commercial Pilot | Civil Aviation School Instructor | University Professor of Aeronautical Sciences | Aviation Expert Witness | Economist | Postgraduate in Aeronautical Sciences, Civil Aviation Safety and Higher Education | Optical Technician
Founder of Instituto do Ar
Sources
Nenhum comentário:
Postar um comentário
Obrigado pelo seu comentário!!!!
Marcuss Silva Reis