elihoole/asrs-aviation-reports huggingface dataset:
Date: 202108
Local time of day: 0001-0600
Location: LAX.Airport, CA
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Service/Access Door
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe; Maintenance Avionics; Maintenance Inspection Authority
Human factors: Workload; Time Pressure; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Aircraft X scheduled for flight to ZZZ at gate X in LAX. The potable water service access panel was on monitor for broken latches. I was assigned to accomplish the monitor to re-tape after water servicing. FAA inspector who was present at the time asked me for a reference to perform the job. I pointed out the number on the monitor sign off work card.  I also tried many times to open it on my iPad tablet before starting the job but was not I successful because of the poor signal at the gate. Didn't have at hand the paper copy reference before starting to perform the re-taping of the access panel when the inspector questioned me about the reference. I called the crew chief office and asked for reference to be printed and sent to me to the gate X because the tablet was working and not reliable because of the poor signal. [Suggestions are to] make sure to have the required paper work or reference on hand before starting the task. Supervisors and crew chiefs have to make all necessary references available as we all have to help each other on to make the terminal operation smooth. The tablet given must be reliable and effective to perform ones task. Trying to make the flight on time can sometimes takes your attention. I could have driven to the office and print the required papers.




Synopsis: Maintenance Technician reported poor WiFi at LAX.
Date: 201705
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Weather elements / visibility: Rain
Light: Dusk
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Navigation Light
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Aircraft; Equipment / Tooling; Procedure
Primary problem: Equipment / Tooling

Narrative: We had a water leak come from the assembly of the beacon light on top of the fuselage of the aircraft. Since the weather wouldn't allow for a proper remove and replace; a deferred action was suggested; in which speed tape would be applied to the affected area to prevent a further leak from arising. The question proposed to maintenance and management was how to proper get to the top of said assembly without walking on the skin or causing any surface damage to the aircraft. Since we lack a lot of the necessary equipment to preformed the task and do it safely; we were talked into basically using a scissor lift; which was not only unbalanced; but entirely unsafe due to the fact we only had one set of fall restrain harness; regardless this was still pushed on to us to get the job done. While the surface was still wet from the earlier down pour of the early mornings rainfall. The harness not only could not properly tether to the lift; but would end up more likely doing more harm than good if one of us were to had fallen while performing this task.Identification: an uneasy feeling of this not feeling right or safe.Cause: lack of proper equipment; and harnesses.Suggestions: provide the necessary equipment to perform any all jobs that involved the top of the fuselage; in a safe and right manner.




Synopsis: A Maintenance Technician reported not having the proper equipment to gain access to the upper rotating beacon on an Embrarer aircraft.
Date: 201211
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Night
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Hydraulic Main System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Training / Qualification
Second reporter function: First Officer; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew FLC complied w / Automation / Advisory; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At altitude; the right hydraulic system failed. Accomplished QRH procedure. Emergency declared and landed uneventfully.


Second narrative: [Narrative 2 contains no additional information.]


Synopsis: A B757-200 right hydraulic system failed in flight so the QRH was complied with; an emergency declared and the flight landed uneventfully at its filed destination.
Date: 202203
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: FCC (Flight Control Computer)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness; Troubleshooting
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: At cruise; (approx 1 hour from landing) ECAM (Electronic Centralized Aircraft Monitor) F/CTL ELAC (Elevator and Aileron Computer) PITCH FAULT 2. Shortly followed by F/CTL ELAC PITCH FAULT 1. INOP systems - Autopilot 1 and 2; Alternate law - loss of protections - Cat 2 - ELAC Pitch. Ran all ECAMS; checklists; QRH; supplemental QRH. No reset option. [Requested priority handling] out of abundance of caution. Requested priority from ATC for descent and approach - long final on long runway. Advised Dispatch; flight attendants; and passengers. Landed on long runway per procedures (direct law - flaps 3) Landing uneventful - taxied to gate. ATC was very cooperative. Notified Dispatch in the air and after gate arrival.Aircraft had previous write ups for same/similar issue. Aircraft had been in ZZZ for 48 hours prior to this flight for same write up. (ECAM F/CTL ELAC PITCH FAULT 1 and 2) and there was a previous write up for ECAM F/CTL ELAC PITCH TRIM FAULT 2.


Second narrative: About an hour from destination; aircraft had an ELAC 1 fail followed by an ELAC 2 failure about 20 minutes later. Followed all ECAM (Electronic Centralized Aircraft Monitor) procedures and QRH procedures. [Requested priority handling]; received excellent handling by ATC. Flight attendants and passengers were notified. Coordinated with Dispatch. Similar events happened during two previous flights based on maintenance logbook entries.Maintenance failed to fix recurring issue.Just need to get aircraft fixed so it does not reoccur. Could be a significant impact to safety if reoccurs in an area with poor visibility; rain/snow; etc.


Synopsis: A319 flight crew reported loss of both ELAC's (Elevator and Aileron Computer) at cruise. Flight Crew requested priority handling and continued to destination airport.
Date: 202005
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Transponder
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Second reporter function: Lead Technician
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Procedure; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: I was assigned the task of 'Drain Flush and Test Pitot/Static circuits' on Aircraft X as outlined in Job Card #XXXX. I accomplished this task while working with Technician B and Lead Technician at Hangar X in ZZZ. We accomplished this task in accordance with the procedures found in the Job Card #XXXX. The Job Card failed to ensure that the Mode S Transponders were disabled preventing test altitudes from being transmitted.Revise the Job Card procedures to include steps to prevent Mode S Transponders from transmitting test altitudes.[Task was related to aircraft] storage [related procedures].


Second narrative: [Narrative contained no additional information.]


Synopsis: Maintenance technicians reported that while performing a test of the pitot/static system on an aircraft; the job card failed to ensure the Mode S transponders were disabled.
Date: 202010
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Human factors: Other / Unknown; Human-Machine Interface
Anomaly: Deviation / Discrepancy - Procedural Weight And Balance; Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Other Person; Person Ground Personnel
When detected: Taxi
Result: Aircraft Equipment Problem Dissipated; Flight Crew Returned To Gate
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: ZZZ ramp planned all the cargo in the aft compartment and all the bags forward. The cargo contained dangerous goods which for some reason the ramp did not notice even though it was on the Dangerous goods form before they even planned the flight. They push the flight out with no bags in the rear compartment and attempted to finalize but couldn't because they had not met the required 15 bags to secure Dangerous Good.




Synopsis: Ground personnel reported Hazmat cargo load configuration errors after gate pushback.
Date: 202109
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Flight conditions: Mixed
Weather elements / visibility: Haze / Smoke; 10
Light: Night
Aircraft: PA-28 Cherokee/Archer/Dakota/Pillan/Warrior
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: AC Generator/Alternator
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument
Human factors: Communication Breakdown; Troubleshooting; Situational Awareness
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Clearance; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Diverted; Flight Crew Requested ATC Assistance / Clarification; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was on an IFR flight plan ZZZ at 4;000 feet in contact with ZZZ center 120.65 when I had a complete electrical failure.  The acrid smell of an electrical fire was evident even though I didn't see any flames.  Fearing a full blown fire I immediately descended toward ZZZ airport which I had in sight.  I was able to contact the ZZZ tower on a handheld radio after I had entered their airspace.  They cleared me to land on Runway XX; which I was able to do.  I was instructed to taxi to the FBO.  Upon arrival at the FBO; I opened the cowling and found multiple melted wires on the engine side of the firewall; with burn damage to the outside lip of the cowling.




Synopsis: PA-28 pilot reported a complete electrical failure required the use of a hand held radio to contact ATC and successfully land at destination airport.
Date: 201706
Local time of day: 1801-2400
Location: ORD.Airport, IL
Light: Dusk
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ORD
Second aircraft: Widebody Transport
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Less Severe
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Rejected Takeoff
Contributing factors: Procedure
Primary problem: Procedure

Narrative: After being cleared for takeoff on Runway 22L at ORD we began our takeoff roll. Between 40 and 50 knots the Tower canceled our takeoff clearance and told us to hold our position. We aborted our takeoff roll using very little brakes and noticed a aircraft that was landing on Runway 28C in front of us. Before we were able to stop completely; the Tower directed us to turn right at taxiway Y; cross Runway 28C; turn right onto November; and cleared us for takeoff again. We did not have a high speed abort; and I used very little braking to slow the aircraft; therefore; the use of the brake cooling charts were not required. We had an uneventful takeoff and continued. During climbout; when time permitted; I contacted the ORD Tower and spoke with a Controller who said that there was no conflict with us and the aircraft because the aircraft did not fly over top of us. The Tower was able to avert a potential mishap by quickly canceling our takeoff clearance. This event is highly unusual for ORD and [I] felt it warranted review.The event happened because ORD Tower cleared me for takeoff too soon. They should have waited for the aircraft to land first.


Second narrative: [Report narrative contained no additional information.]


Synopsis: B737 flight crew reported ORD Tower canceled the takeoff clearance on Runway 22L because of conflicting landing traffic on Runway 28C.
Date: 202012
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Elevator Trim System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Distraction
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Diverted
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was the Pilot Flying. On climb-out I noticed my electric trim was not working. The First Officer's electric trim was also inoperative. We leveled off to assess the situation and complete the QRH checklist. We elected to return to ZZZ.




Synopsis: B737-700 Captain reported the Electric Pitch Trim failed on both the Captain's and First Officer's control columns.
Date: 202011
Location: VHHH.Airport, FO
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Reporter organization: Air Carrier
Reporter function: First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport; Human Factors; Chart Or Publication
Primary problem: Chart Or Publication

Narrative: HKG Runway 7L/25R is closed for construction; but there is no NOTAM for this condition. It does show on the ATIS. I'm told this condition has been ongoing for a while; and I'm also told that it's been previously reported. Why is there no NOTAM for a runway closure? If the local authority will not issue a NOTAM; then our company should issue an internal NOTAM. This runway closure makes HKG a single-runway airport with diversion options that are limited and/or undesirable.




Synopsis: Air Carrier First Officer reported a runway at this location is out of service and there are no NOTAMs.
Date: 201810
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Icing
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Landing Gear
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: Ferry flight. Previous to flight I knew maintenance was determining whether the flight would be flown with the gear down and locked or gear up. Due to icing conditions we had to go gear up. Ferry permit was adjusted and we left. Once airborne the gear would not raise. While the CA (Captain) was hand flying; the FO (First Officer) used the solenoid switch to raise the handle. Gear did nothing; but soon followed a gear disagree warning message; WOW (Weight On Wheels) Output caution message; Nose Wheel Steering Inop Caution Message; and a Prox Sys 1 Fault status message. We ran the QRH procedures; which basically had us land with no nose wheel steering and unpressurized the airplane as well as manually deploy the spoilers on landing. We did [notify ATC]. Asked for a tug to be available to tow from the runway; also asked for them to verify gear down on final (both Tower and an aircraft over the approach end verified for us they were down) and landed without further incident. After coming to a stop; I tried to cycle the nose wheel steering switch in hopes of being able to move ourselves off the runway with no luck. Tug came out. We did the procedure for two engines shut down and prepared to finish the WOW checklist prior to power down. Called maintenance upon parking and they told us we did not need to comply with the WOW checklist that had us pulling a bunch of circuit breakers to prevent the ADG from deploying since the WOW message disappeared and the prox sys message disappeared. Called [Operations] and scheduling for further guidance.




Synopsis: CRJ-900 Captain reported the landing gear failure to retract was accompanied by several caution messages.
Date: 201509
Local time of day: 1201-1800
Location: WSJC.ARTCC, FO
Flight conditions: VMC
Light: Daylight
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
ATC / advisory: Center WSJC
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airspace Structure; Human Factors; Procedure
Primary problem: Ambiguous

Narrative: We were intercepted by two SU 27/30 Indonesian fighter aircraft over TOMAN intersection. We had a clearance to cross 45 miles to the east of HOSBA at FL 140 from Singapore Radar. We were complying with clearance when we got a Traffic Alert and then another. We let Singapore Radar know what was going on....Then we received a Resolution alert to climb. We did this. We received many resolution alerts which we followed till we could see the aircraft! We then let Singapore Radar know what was going on of course and why we were not descending and instead climbing! We continued to tell the Indonesians we did have approval to be in their airspace. They were saying we did not have permission to be in their airspace...We took out the release just to make sure it was there ...They still kept saying you have no right to be in Indonesian airspace you have no clearance!! We argued for a while on guard. The Captain then told me I had the plane and radio and he got on guard freq. and told them to back off a couple of times and that we were continuing to Singapore... They started backing off as they said; so you're real macho!! I feel this put not only our lives at risk; but also the passengers on the aircraft...As they were flying really close to the aircraft. As the Indonesians were not complying with any Singaporean request to identify themselves as Singapore is controlling this airspace... Singapore was also making these requests on Guard freq. to no avail...




Synopsis: A B757-200 First Officer reported they were intercepted by Indonesian fighters even though they felt they were properly cleared into the airspace.
Date: 201701
Local time of day: 1801-2400
Location: ZZZZ.Airport, FO
Flight conditions: VMC
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Aircraft component: Fuel Quantity-Pressure Indication
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Fuel imbalance; possible fuel leak. Followed all SOPs. Informed ATC of aircraft condition and requested emergency equipment. Uneventful landing and gate arrival.  Fully debriefed with crew; dispatch; Duty Manager and Maintenance Control.




Synopsis: B777 Captain reported of a fuel imbalance which was caused by a possible fuel leak or malfunctioning fuel gauge. ATC was advised and a normal landing ensues.