elihoole/asrs-aviation-reports huggingface dataset:
Date: 201708
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Training
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Aircraft component: Brake System
Component problem: Malfunctioning
Reporter organization: FBO
Reporter function: Trainee
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Other Stuck on the Runway
Result: General Physical Injury / Incapacitation; General Maintenance Action
Contributing factors: Procedure; Human Factors; Aircraft
Primary problem: Human Factors

Narrative: Student was sent on his 4th solo to go to the north practice area and to do landings at ZZZ. About an hour into my student's flight he calls me and states that he thought the brakes were locked up after landing and he was still on the runway. He then got out of the aircraft with the engine still running to check the brakes out to see if he could fix it. After getting out of the aircraft he was struck by the propeller on his hand. He had been instructed to never get near a moving propeller and to never get out of an aircraft that is running. After being struck he then got back into the aircraft and was able to taxi the aircraft to an FBO and walked in by himself and was able to procure assistance from the staff inside then proceeded to the hospital.




Synopsis: An instructor reported that his student; flying a light sport aircraft; was stuck on a runway with the brakes locked. The student injured himself in an attempt to check the brakes.
Date: 202010
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Human-Machine Interface; Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel; Person Maintenance
When detected: Routine Inspection
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was working on the dock my normal job assignment is to receive parts and ship out parts out. I was made aware that I may have mistakenly shipped out a Hazardous material part. I was unaware of this at that time. I truly don't remember shipping it out. I'm aware of the Hazardous material policy and would have not shipped out the part if I knew it was Hazardous.




Synopsis: Air Carrier Maintenance Stock Clerk reported being notified that he shipped a Hazardous material part. Stock Clerk is aware of SOP of shipping Hazmat but does not recall the event.
Date: 201309
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Dusk
Aircraft: Embraer Legacy 450/500
Operator: Fractional
Operating under: Part 91
Flight phase: Parked
Reporter organization: Fractional
Reporter function: Lead Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Pre-flight
Contributing factors: Company Policy; Human Factors
Primary problem: Human Factors

Narrative: Before departure; the Captain went to pull the [wheel] chocks. The Lineman [Mechanic] told him that he would take care of it but the crew member insisted that he would pull them. The Lineman then explained to him that for safety reasons and Station safety policy; they don't pull the chocks until the Ground Power Unit (GPU) power cord connected to the aircraft is disconnected. That crew member impolitely said that he's following his own policy and that he was going to instruct our company on how he strongly disagrees with this policy and went ahead and pulled the chocks anyway. The policy was set in place due to multiple times of the aircraft inadvertently rolling forward while the crew members were performing Pre-flight Checks. Several aircraft and GPU's were damaged when the cord was stretched to full length. Crews sometimes release brakes and lessen foot pressure accidently; causing the aircraft to roll forward; prior to providing the disconnect signal to the Lineman. This Local Base policy prevents 2-3 potential GPU incidents each year.




Synopsis: A Maintenance Manager describes his efforts to discourage a Captain from pulling the wheel chocks from an Embraer EMB-505 aircraft during pre-departure operations. Pilot disregards request; ignoring the safety concerns of Maintenance personnel and company Station safety policy.
Date: 201606
Local time of day: 0001-0600
Light: Daylight
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Drinkable/Waste Water Syst
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Workload
Second reporter function: Flight Attendant In Charge
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: In-flight
Contributing factors: Company Policy; Aircraft; Human Factors
Primary problem: Company Policy

Narrative: Approximately two hours prior to landing; I was advised by my crew that we had only 35 gallons of potable water balance in the flight. I advised my crew to modify the arrival service so as to conserve water in the lavatories for washing of hands and flushing by pax and crew. We did have about four-six liters of bottled water which were saved to be placed in lavs if required in addition to hand sanitizers.About an hour prior to landing the console reading was 1 gallon. At this time; Waste tank no.1 alerted us to an INOP status and four lavs were unusable for the remainder of the flight.This has been an ongoing issue with this airplane/flight for over two years now. It is a health and safety issue which the company has not addressed adequately in all this time.Pax and crew; as primary food handlers; have limited facilities and tools to wash their hands; use lav facilities as well as flush toilets. It is unhygienic; unsanitary and a health hazard.


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


Synopsis: Flight attendants on international flight reported a chronic issue with insufficient water to last the duration of the trip.
Date: 202109
Local time of day: 1801-2400
Location: MRJ.Airport, WI
Flight conditions: VMC
Light: Dusk
Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZAU
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial; Flight Crew Multiengine
Human factors: Communication Breakdown; Other / Unknown; Distraction; Situational Awareness; Time Pressure; Workload
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Aircraft Y nearly collided with me in my Aircraft X. I had all anti-collision lights on at dusk; this aircraft had no lights on until approximately 30 seconds after the near collision. The aircraft approached from the right at approximately a 30 degree intercept angle. I did not spot the aircraft until it was roughly 100 feet away at which point I took evasive action and dove my aircraft. Had evasive action not been taken we would have certainly collided. The other aircraft took no evasive action and did not seem to notice my aircraft until I had passed on the other side of them at which point they turned on their lights.




Synopsis: GA pilot reported an NMAC while in cruise flight requiring evasive action. The other aircraft did not have any lights on.
Date: 202201
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: CTAF ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Communication Breakdown; Confusion; Situational Awareness
Second reporter function: Captain; Pilot Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: Aircraft Aircraft Damaged; Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Aircraft

Narrative: Taxied out to Runway XX at ZZZ as planned and briefed. Nearing departure end we got an Eng 2 Reverser fault. Stopped and reviewed QRC. Nothing for on ground event noted. Called Maintenance Control. Decided to taxi back to ramp to clear taxiway and work issue. Taxied via Runway XX and exited at Taxiway XX. Parked on south side of Deice Ramp. Maintenance Control directed to start APU. Captain set brakes and we started APU. Upon direction from Maintenance Control; we shut down both motors. Captain stood up to check circuit breaker panel. CB at N41 on 121 VU panel was popped; labeled Engine 2 Oil Quantity Sensor Channel B.Upon Maintenance Control direction; we reset circuit breaker. We were directed to restart engines and report back. Started Engine 1. At 50% N2 the FO (First Officer) started Engine 2. Normal indications; when radio call reported engine fire on right side. FO looked right and saw some smoke blowing past the right window. Then the fire alarm and ECAM illuminated. FO looked up to verify indication and pointed to ECAM screen. Started to read the first step and alarm stopped and ECAM went away. Radio call reported sparks from bottom of Engine 2. There was a momentary alarm bell again and then it went away. Fire loop fault appeared and FO shut down motor with Master Engine switch. No other indications of fire noted. Airport CTAF called fire department. Crew stayed on phone with Maintenance and fire department reported a burn-through on the cowling and scorching on the cowling. Crew elected to taxi to Parking with fire department concurrence. Shutdown went normal. Passengers deplaned via air stairs. Normal checklists completed.


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


Synopsis: A320 flight crew reported an engine fire and engine cowling burn-through while troubleshooting an engine reverser fault on the ground with Maintenance Control.
Date: 202105
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class C ZZZ
Aircraft component: Coalescer Bag
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight; Taxi
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After gate arrival the flight attendants reported a strong odor like 'dirty socks' on descent.  They said it started in the aft cabin and progressed throughout the cabin.  No odor was noted on the flight deck.




Synopsis: Captain reported Flight Attendant notification after gate arrival of 'dirty socks' odor throughout the cabin.
Date: 201210
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Ferry / Re-Positioning
Flight phase: Cruise
Airspace: Class G ZZZ
Aircraft component: Fuel Distribution System
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer
Human factors: Training / Qualification; Situational Awareness; Time Pressure; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Landed As Precaution; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was ferrying a Breezy (experimental) for a friend.  I had topped the tanks with fuel so it had at least 20 gallons on board.  About 20 minutes after takeoff at an altitude of approximately 1;000 feet AGL the engine started running erratically and cutting out.  The terrain below was all tall pines except for a clear strip of land where a pipeline had been run.  Since the engine was not producing full power I elected to circle that clearing while I tried to remedy the engine problem in the event I would need to land the airplane.  I could not get the engine to produce full power; so rather than head westward over the tall pines and risk a crash landing and/or accident in the heavily forested areas; I elected to make a precautionary landing on the pipeline clearing.  I landed the airplane in the clearing and did absolutely no damage to the airplane; myself; or any property whatsoever.  A couple of days later the owner of the airplane trailered it home. When the owner was draining the fuel out of the wing tanks prior to disassembly of the airplane for transport after about two gallons of flow the fuel line from the wing tanks to the carburetor stopped-up.  As of this time he has not done any further investigation; but of course he will.  We were running 100LL fuel but the previous owner ran nothing but autogas.I did not contact the FAA or file an incident or accident report of any sort because the event in my interpretation of the definitions of an incident or accident in the FAR's and AIM did not apply or require such. The event was simply a precautionary landing. The landing prevented a possible accident or incident.




Synopsis: A Breezy engine lost power because of a blocked fuel line so the pilot landed the aircraft on a deforested pipeline area with no aircraft damage or injury.
Date: 201701
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Airliner 99
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Aircraft component: Landing Gear
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Pilot Flying
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After takeoff; the landing gear did not retract when I selected the gear handle up. I selected gear down and noted that I only had green lights for the main gear. The gear handle was still illuminated red and the landing gear circuit breaker was out. Retarding the power levers and extending the flaps both activated the gear warning horn. I manually lowered the gear and received three green lights. The gear horn did not sound when I extended the flaps or retarded the power levers. I landed without further incident.




Synopsis: C99 pilot reported being unable to retract the landing gear and received an unsafe nose gear indication when the handle was returned to the down position. Manual gear extension was performed and resulted in a normal landing.
Date: 201901
Flight conditions: VMC
Light: Daylight
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Aircraft component: Engine Exhaust System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Flight Attendant In Charge
Second reporter function: Flight Attendant (On Duty)
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor; Ground Event / Encounter Other / Unknown
Detector: Person Flight Attendant; Person Passenger
When detected: Other Engine start
Result: General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Passengers noticed flames shooting out of the [aircraft's left] engine followed by a lot of smoke. Passengers noticed a lot of smoke on [the aircraft's right] coming out of the engine. We reported it to the Captain and Maintenance came out and checked out the aircraft. We had fume issues with the same aircraft the day before.


Second narrative: On taxiing during the safety demo playing; [I] was alerted by a passenger on [the] aircraft's left advising that there was smoke and fire coming out of the engine. Passengers [on the aircraft's] right then advised smoke coming out of engine. Aircraft left engine fire was encompassing the windows along with smoke. Same aircraft as the day before.


Synopsis: A330 flight attendants reported passengers informed crew of flames shooting out of engine exhaust on start. Cabin fumes became prevalent in passenger cabin.
Date: 202105
Aircraft: B737 MAX Series Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Aircraft component: Aircraft Logbook(s)
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Confusion; Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Equipment / Tooling; Human Factors; MEL; Aircraft; Procedure; Software and Automation
Primary problem: Software and Automation

Narrative: While signing off work steps on the electronic device Maintenance application; electronic sign-off allows the technician to N/A the step even when not allowed per GMM.  E/A XXXX-XXXXX does not allow for N/A to be used. therefore the option shouldn't be allowed in the maintenance application.




Synopsis: Technician reported that when using the maintenance application for electronic log book sign offs; it allows the use of 'Not Applicable' for entries; which is not allowed by the Engineering Authorization.
Date: 201201
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Oil Temperature Indication
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Second reporter function: Pilot Not Flying; Captain
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed As Precaution; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While cruising at FL320 over the mountains in day VMC conditions; we noticed that the left engine's oil temperature was increasing. The temperature seemed somewhat erratic; but the general trend was upward. We subsequently saw the yellow light and then the red light. The highest temperature I saw was about 180 degrees. We ran the Oil Temperature High QRH procedure. The Captain declared an emergency and we got clearance to divert. During the descent; I flew the airplane while the Captain ran the Engine Failure/In flight Shutdown QRH procedure. A deadheading pilot in the jumpseat provided excellent backup monitoring altitude clearances; pulling out the approach plates and so forth. We had an uneventful landing the weather was VMC with little or no wind. We stopped the aircraft on the runway. The Fire Chief and his team looked the aircraft over and saw no evidence of fire; smoke; or anything leaking. We then taxied the airplane to the gate.The mechanics later said that they found a broken wire. Are the wires in this area getting old? Are they flexing repeatedly so that they eventually break? If this is a common occurrence; perhaps these wires should be inspected during periodic maintenance checks.


Second narrative: I am filing this report for an in-flight shutdown of an engine and overweight landing. At cruise altitude; the left engine oil pressure began increasing above the limits. In accordance with the QRH; the left engine was shutdown. An emergency was declared and an overweight landing was accomplished. I am not aware of any deviation from either company procedures or FAR's; but am filing this report in the event that a violation is filed.


Synopsis: MD83 flight crew experiences high engine oil temperature at FL320 and diverts to the nearest suitable airport. The engine is shut down; an emergency is declared; and an uneventful landing ensues. A broken wire is found to have caused a false indication.
Date: 201410
Local time of day: 1201-1800
Location: ORF.Airport, VA
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Initial Approach
Airspace: Class C ORF
ATC / advisory: TRACON ORF
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Conflict Airborne Conflict; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: While Flying at 3;000 feet on downwind into Norfolk I noticed an object off the left side of the aircraft less then 200 feet below us and 1/4 mile to our Left; The object was not a plane and did not appear to be balloons. It did however appear to be some sort of Unmanned Aerial System. We advise approach of the event and followed up with a call once on the ground. After calling tower I called the Dispatch supervisor and the Chief Pilot.




Synopsis: An air carrier Captain; on downwind for landing at ORF; observed an apparent unmanned aerial vehicle some 200' below and 1/4NM to the left of their flight.