elihoole/asrs-aviation-reports huggingface dataset:
Date: 201906
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Light: Night
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ramp ZZZ
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Situational Awareness
Anomaly: Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: Taxi
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Prior to engine start during push back; the flight attendants called and reported a 'chemical smell or dirty sock smell.' We elected to terminate the push back and were pulled back into the gate. We turned off the packs and the APU bleed air. We deplaned the passengers and crew and accomplished the QRH for smoke odor/fumes. While exiting one passenger began having symptoms of nausea and vomited. We called Paramedics. After deplaning 2 FAs began having headaches and paramedics treated them in the terminal. No one was transported to the hospital.




Synopsis: Captain reported Flight Attendant notification of 'chemical or dirty socks' smell during pushback for departure. Crew returned to gate for Maintenance. Deplaned with a passenger and two flight attendants experiencing health issues.
Date: 201507
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Dash 8-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower ZZZ
Aircraft component: Hydraulic System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After landing; we used mostly reverse thrust to slow the aircraft and exited the runway. We had to use only minimal braking to stop the aircraft at the gate. However; when the main cabin door opened; the rampers came up and told us to look at the wheels (on the aircraft left side) because they were smoking. I went outside to look and saw that the wheels were in fact smoking. Based on previous experience with a brake overheat issue that nearly resulted in a fire; and because I thought it was the safest course of action; I preemptively called ARFF to come to our gate. We also made a phone call to Dispatch to inform them of the situation. The passengers deplaned normally during this time. The smoke was not thick enough to be readily noticeable to passengers; nobody became alarmed. After the firefighters arrived; they determined that the brakes did not overheat as we suspected; but rather some sort of fluid (hydraulic fluid) had dripped on the brakes and was evaporating visibly. The firefighters measured a brake temperature of only 140 C. They left and maintenance showed up. They determined that there was a hydraulic leak in the nacelle; above the wheels. The aircraft was written up and handed over to maintenance.




Synopsis: Dash 8 Captain reported ramp personnel spotted smoke in the brake area after parking at the gate. Cause of the smoke was determined to be hydraulic fluid leaking onto the brake area.
Date: 201812
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Cessna 402/402C/B379 Businessliner/Utiliner
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Shortly after rotation; while the First Officer was retracting the gear; we felt a shudder in the right engine. It continued to produce full power; but shortly thereafter started to produce only partial power. I then took over the flight controls and ran through the Engine Failure after Takeoff flow. The right engine regained full power after the aux pump was selected to high. After climbing through 1;100 feet MSL; the First Officer ran through the QRH. We elected not to shut down the engine; as it was still producing power. I elected to set 'single engine cruise'/normal climb power as we flew the regular left traffic pattern back to [departure airport]; as that seemed to produce the most stable power throughout our return to the airport. I then ran the normal In Range and Before Landing flows and checklists. The right engine did start to run rougher on short final; most likely due to the high aux pump setting; but we were able to maintain control and the appropriate approach and landing speeds and land safely. Upon landing rollout; the right engine quit; but we were able to continue a taxi off the runway; then safely to the gate.


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


Synopsis: C402 flight crew reported returning to departure airport following an engine issue.
Date: 201905
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Pre-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: While scanning boarding guests; I overheard that one had allegedly left her laptop in the bag that was checked at the gate. I immediately approached the guest and she confirmed. I notified the [flight crew] ASAP; while the passenger spoke to a ramp personnel who happened to be in the jet bridge at the moment. When a Gate Agent came by; I informed her as well. However she was quite reluctant and showed little enthusiasm in retrieving the luggage. The same [Gate Agent] had been quite 'pushy' in starting the boarding process; although she did not ask me whether the minimum crew were on board and the temperature were safe to board; not taking into consideration that it was still not [time to board] and the flight was not full. I suspect the boarding agents did not ask the vital question; whether the guest had any devices with lithium battery in the bag they were checking. The guest admitted she was not asked the question; however she was a bit 'frazzled'. The Captain ran down the ramp and did everything he could to locate the bag in an expeditious manner!On behalf of all airline crews who are enclosed in the flying tubes with - at times - no opportunity to do emergency landing; and in the light of the recent fatal fires on foreign carriers; I beg [gate agents] to pay more attention to the type of the issue - rather than just rush to board & close the door ASAP; as safety should be paramount!




Synopsis: Flight Attendant reported passenger inadvertently checked baggage containing laptop with batteries installed.
Date: 201606
Local time of day: 1201-1800
Location: MYF.Tower, CA
Light: Daylight
Aircraft: PA-46 Malibu/Malibu Mirage/Malibu Matrix
Operator: Personal
Operating under: Part 91
Flight phase: Taxi
ATC / advisory: Tower MYF
Second aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Reporter organization: Government
Reporter function: Instructor; Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Situational Awareness; Training / Qualification
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Rejected Takeoff
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Training in progress on Local; I was the OJTI. Aircraft X landed runway 28R; and my student instructed Aircraft X to exit taxiway Foxtrot hold short of Runway 28L and remain this frequency. Aircraft X gave an incomplete readback of hold short instructions. My student corrected the pilot and then Aircraft X gave a complete and accurate readback of hold short instructions. My student then cleared Aircraft Y for takeoff on runway 28L. As I was watching the situation develop; it appeared that Aircraft X was getting very close to the runway; at which point I jumped in and canceled the takeoff clearance for Aircraft Y twice; to be sure the pilot heard it. As Aircraft Y was decelerating; Aircraft X was about halfway through crossing runway 28L. Aircraft X was then issued the Brasher warning.




Synopsis: MYF Local Controller Instructor reported of a runway incursion and ground conflict because of an aircraft that crossed halfway onto the runway while a departure aircraft was told to stop twice. The crossing aircraft read back hold short instructions.
Date: 201311
Local time of day: 1801-2400
Location: ZFW.ARTCC, TX
Aircraft: Super King Air 300
Flight plan: IFR
Flight phase: Descent
Airspace: Class A ZFW
ATC / advisory: Center ZFW
Reporter organization: Government
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I was working alone on Turkey. We were split with Raider-ultra high. Because of this the traffic wasn't heavy; but due to the circumstances; it was abnormally task-complex. We had Lancer active in low up to 260; an aircraft that had just left Lancer split between my altitudes and Raider; as well as another entering my altitudes and Lancer. At the same time I had a SJT arrival that INK/LEE wanted turned out for their MAF departure. I also had a flight of two re-fuelers coming from INK/LEE that were breaking up and an aircraft coming from BGD-L trying to descend into CVS-A who couldn't hear me. The aircraft of subject was a BE30 landing MAF who I have a PD descent to FL240 and handed off to LBB-L and switched. This is obviously where I dropped the ball; becoming consumed with the other tasks happening relatively at the same time while dealing with bad rides and poor frequencies. I lost focus until the BE30 had already crossed 61/82's boundary; at which point I called and pointed him out. I have long felt that unless the traffic volume is incredibly heavy; it's much more advantageous to have a D-Side than have the ultra high sector open. For issues such as this; a D-Side to make/take calls is much more effective; where the coordination can be alleviated off the R-Side. That being said; much of this came on quickly so it would've been hard to anticipate such events to accumulate at once. If I had any suggestions for myself or supervisors it'd be to recognize when complex issues are rising and add a D-Side rather than have an ultra high sector open on a normal traffic volume afternoon; especially one with issues like we had today with poor frequency reception on both ends and bad rides; resulting in more frequency congestion by the R-Side; tying up time needed to coordinate.




Synopsis: ZFW Controller experienced an airspace infraction when internal coordination requirements increased the workload significantly; the reporter arguing that a D-Side would be more helpful than 'splitting' the sector.
Date: 201603
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Ground Event / Encounter Object; Inflight Event / Encounter Object
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Parked at gate waiting for jetway. I was told by ground personnel that the jetway driver hit the engine. I didn't see any damage and did not write anything up because the local ops people said they have maintenance coming to check to be sure.




Synopsis: A319 Captain was informed after parking that the Jetway may have made contact with the left engine at it was maneuvered to mate with the aircraft. No damage could be detected but Maintenance was called.
Date: 201310
Local time of day: 0601-1200
Location: ZAN.ARTCC, AK
Flight conditions: VMC
Light: Daylight
Aircraft: Widebody; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZAN
ATC / advisory: Center ZAN
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Human factors: Situational Awareness; Distraction
Anomaly: Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: I was the Pilot Flying. Level at FL 340 nearing the TED VOR (ANC) when the Pilot Monitoring and I noticed a large white balloon at out 2 o'clock position within 1/2 mile laterally from us on our right and what appeared to be about 200 feet above us. The balloon was very large similar to a weather balloon with a large device suspended below it about 20 feet. The suspended device was attached via three connections and was viewed with enough detail that the size was rather large. It could have been closer; but at 450 knots ground speed it all happens rather quickly. Can't image what would occur if that we would have made contact.  A report to ATC was made via VHF radio call to the Controller. Transponders should be affixed to these devices when there are in the upper airway structure so that ATC can maneuver aircraft around them.




Synopsis: An air carrier at FL340 near TED in ZAN airspace flew with half a mile and 200 feet of a very large balloon with a large device suspended beneath it.
Date: 201508
Local time of day: 1201-1800
Location: STP.Airport, MN
Flight conditions: VMC
Light: Daylight
Aircraft: UAV - Unpiloted Aerial Vehicle
Operator: Personal
Operating under: Part 91
Flight plan: None
Airspace: Class D STP
Second aircraft: Robinson R44
Reporter organization: Personal
Reporter function: Observer
Reporter qualification: Flight Crew Private
Anomaly: Conflict NMAC; Deviation / Discrepancy - Procedural FAR
Detector: Person Observer
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I was a pilot on the ground in Battle Creek Park approximately 1 mile east of STP. I noticed a drone hovering on the base leg VFR approach to Runways 13 and 14 due north of my position and at the same altitude that a R44 helicopter was operating that day. This is not a good place to be operating a drone. I've flown this approach to STP in the past in a helicopter; and I don't want to hit a drone coming into land at STP. The R44 helicopter I saw was lower than the drone was today.




Synopsis: Private pilot observing from the ground; reports a NMAC between an R44 helicopter and a drone during a visual approach to Runway 13 or 14 at STP. The drone was hovering near the base leg of the VFR traffic pattern and 100 feet above the helicopter.
Date: 201511
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Aircraft component: Powerplant Fire Extinguishing
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Maintenance Action
Contributing factors: Company Policy; Aircraft; Human Factors
Primary problem: Human Factors

Narrative: Numerous B737 aircraft have dirt and debris that cover the Fire Control and Radio panels in the cockpit. Whenever a maintenance Logbook write up is made; the action is deferred and not done. I have sent images and emails to the CEO; System Chief pilots; Chief pilots; Assistant Chief pilots; etc over the previous months and the cockpits are still not being cleaned. [Affected components]: Flight Deck Displays. Instruments. Airworthiness [concerns].




Synopsis: A pilot reported numerous company B737s had dirt and debris accumulation that covered the Fire Control and Radio panels in the cockpit. Logbook write-ups resulted in Maintenance deferrals with Flight decks still not being cleaned.
Date: 201501
Local time of day: 1201-1800
Location: MKE.Airport, IL
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E ZAU
ATC / advisory: Center ZAU
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Confusion
Anomaly: Deviation - Speed All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Chart Or Publication; Procedure
Primary problem: Chart Or Publication

Narrative: On the ACCRA SID out of MKE after 10;000 feet; we indicated 300K.  When Center said we could resume normal speed we then saw on chart that 250 knots was the speed.  We both checked and talked about the SID before pushback and did not see speed restriction. The 250 speed restriction needs to be easier to notice.




Synopsis: The flight crew of an air carrier twin jet departing MKE on the ACCRA RNAV SID failed to note the restriction to maintain 250 knots until advised by ATC. They cited the format of the chart as a contributing factor.
Date: 201310
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Dash 8-100
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Aircraft component: Powerplant Mounting
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown; Confusion; Situational Awareness; Workload
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Maintenance
When detected: Other After Aircraft Departure
Result: General Maintenance Action
Contributing factors: Human Factors; Incorrect / Not Installed / Unavailable Part
Primary problem: Human Factors

Narrative: Number One engine outboard side mount was written up for failed Drift Check.  Mechanic changed mount bracket and attaching hardware only.  Other side mount assembly components were not taken out of the box and changed as required.  The task was accomplished during Routine Overnight Maintenance (RON) and completed on the next shift.  Incoming Lead Mechanic put supposedly all removed engine side mount components on Supervisor's Review cart after asking outgoing Lead Mechanic if those were the old parts which he confirmed.   It was determined that [some] parts were not changed out as required when one Supervisor reviewed parts for turn-in/ repair.  Note: Another Supervisor previously signed turn-in rotable for old parts that still had the new parts in the box. The Task of changing the engine mount was written up as a discrepancy as part of a scheduled engine removal and re-install on a weekend aircraft project. Maintenance Control was notified and Chief Inspector was consulted for any and all actions to be taken at the time of discovery. [Recommend] all Maintenance personnel should be reminded that any parts replaced on an aircraft requires complete removal of assembly and turned in as a complete assembly at the time the maintenance action has started.  Maintenance personnel should ensure that any sign-offs for removal and replacement of assembled components are actually complied with (example all new parts taken out of box and old ones immediately turned in). [Improper Maintenance noticed] after aircraft dispatched.




Synopsis: After realizing that a #1 Engine mount change was only partially completed on a DHC-8-100 aircraft that had already departed; an Aircraft Maintenance Technician (AMT) recommends that all Maintenance personnel should ensure that any sign-offs for removal and replacement of assembled components are actually complied with.
Date: 201305
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke; 7
Light: Daylight
Aircraft: Eurocopter AS 350/355/EC130 - Astar/Twinstar/Ecureuil
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Passenger
Flight phase: Cruise
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: GPS & Other Satellite Navigation
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Commercial
Human factors: Communication Breakdown; Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Other Person
Result: General None Reported / Taken
Contributing factors: Aircraft; Airspace Structure; Human Factors
Primary problem: Human Factors

Narrative: Flying Electronic News Gathering we were sent up to near the state border to a very small town for a bank robbery. We launched almost immediately to go flyover the scene for the TV station. Before we departed I did not check for TFR's but did check weather considering I did turn down the flight earlier in the day for less than ideal flying conditions. We were over the scene for about 30 minutes and judging by the seriousness of what took place I did maintain a higher than normal altitude but was limited to the ceilings of about 1;700 FT MSL at the time. Upon my return I was notified by a fellow pilot about the TFR and after I returned I checked the FAA website and the TFR was in place. I operate with a 496 Garmin GPS with TFR information and it showed nothing in the vicinity and this feature has not let me down in the past. I was surprised not only by the nature of the TFR; its' location; and not showing up on the GPS that it existed at all. I will from now on make sure I check for TFR's before each flight and not rely on the GPS for that information.




Synopsis: Helicopter pilot reports discovering after landing that he had been operating in a TFR. A 496 Garmin GPS with TFR information was in use during the flight and did not show the TFR.