elihoole/asrs-aviation-reports huggingface dataset:
Date: 201509
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Gulfstream G200 (IAI 1126 Galaxy)
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Cockpit Window
Component problem: Malfunctioning
Reporter organization: Air Taxi
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The first two legs of the trip were uneventful.  While level at FL430; Mach .80 in smooth air; the LH Cockpit Windshield shattered.  It was an explosive shattering; sounding like someone had struck the cockpit with a baseball bat; but fortunately the windshield did not depart the aircraft; or begin leaking air that we could tell.We immediately went on 100 percent oxygen and secured our shoulder straps; and I then asked ATC for a descent to FL280; advising them we were experiencing some windscreen delamination and wanted to reduce our cabin pressure.  We were given a descent and [the First Officer] slowed the aircraft to Mach .70 during the descent; then 270 knots IAS after leveling off.  During the descent I switched the cabin pressurization system to manual and raised the cabin pressure to between 9;000 - 10;000 feet; establishing a cabin differential of approximately 4.5 psi.I called Dispatch on the satphone to advise them of the issue and get divert instructions from Maintenance.  We stayed at FL280; 270 KIAS until given a descent on the arrival into [our divert airport]; and I monitored the electrical page on my side to watch for windshield arcing (we elected to leave the windshield heats on Low); and continued to manually adjust the cabin pressure throughout the descent to maintain a minimal cabin differential.The landing was uneventful; the ship was written up and turned over to [the] maintenance department.




Synopsis: A G200 Captain reported they experienced left cockpit windshield delamination at FL430. The flight diverted to a suitable airport.
Date: 201705
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Other Documentation
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Ground Personnel
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While maintenance was servicing the #2 engine; they had a red placard in the cockpit panel telling anyone in the cockpit the plane was being repaired and do not operate. The out bound crew removed the placard and proceeded to do their check list. When they turned on the fuel pumps the #2 engine started to pour fuel all over the ramp causing a large fuel spill. If a mechanic had been under the engine; he would have been covered in fuel.




Synopsis: A ramp service employee reported the flight crew disregarded a maintenance-in-progress placard and began to operate systems as called for in the preflight checklist.
Date: 201601
Local time of day: 0001-0600
Location: ZJX.ARTCC, FL
Light: Night
Aircraft: B757-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZJX; Special Use W-161B
ATC / advisory: Center ZJX
Second aircraft: Fighter
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion; Situational Awareness; Distraction
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Air Traffic Control; Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: I was working sector 52 combined up with the north part of sector 51. The warning areas referred to as Double Shot were hot from the surface to FL500 in the western half of the airspace and in the eastern portion of the airspace the warning areas were active from the surface to FL300. It is common procedure for air carriers and GA to transition Double Shot airspace via AR4. Double Shot handed Aircraft X off to me at FL290 eastbound transiting the warning area airspace. As Aircraft X was travelling eastbound I noticed an intruder track at FL270 travelling towards Aircraft X; as the intruder target got closer to Aircraft X I noticed the target start to climb. When the intruder was at FL285; I issued a traffic alert to Aircraft X. The pilot of Aircraft X stated that they had the aircraft on TCAS but could not see the aircraft. The intruder target then descended rapidly down and stopped its altitude squawk. I immediately called Double Shot over the land line and asked if they knew who the intruder was and what it was doing. Double Shot told me that the aircraft in the warning areas were capped at FL270 and below. I told them that this was obviously wrong since Aircraft X had just been buzzed by the intruder aircraft. I was not in communication with the intruder target and had no information about who he was or what he was doing. Double Shot said they would take care of it and that was all I heard from Double Shot. Aircraft X proceeded on course without further event.Double Shot often has problems getting a hold of the fighter pilots in the warning areas. Double Shot should be able to get a hold of any and all aircraft in the warning areas at any given time and they should know exactly what each and every aircraft under their control are doing.




Synopsis: ZJX Controller reported another facility handed off an aircraft to him. The Controller then sees a target in the warning area climbing towards the aircraft just handed off. Controller issued traffic and called the other facility.  Other facility stated aircraft is restricted to a specific altitude. Aircraft busted altitude and buzzed the aircraft just handed off. Controller reported the violation to the other facility.
Date: 202012
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: APU Pneumatic System & Ducting
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: Pre-flight
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: This [anomaly] was isolated to the APU bleed and even when MX (Maintenance) was still smelling the odor they still signed the aircraft off; given that it went away with engine start. An APU MEL should have been the first thing they did here instead of trying to get the aircraft back out into service. I as Captain was doing the preflight for our flight from ZZZ to ZZZ1. During the preflight we had a fume event once I selected the APU bleed on. The estimated duration of the event was about one minute. The foul smell came on very strong and immediate. Even with our face coverings (per COVID policy) on in the cockpit it still overwhelmed us; it was that strong. I immediately turned the APU bleed off and opened the cockpit windows. Maintenance then came to the aircraft and did their procedure agreeing the smell was throughout the entire aircraft and coming through on both packs. MX did their procedure and once it was returned to service I had them explain what they did. [MX response] an engine run at the gate and a pack burn. Once we stepped back on the aircraft we still could smell the lingering odor and when I asked about it he said; oh it goes away once you get the engine started'. I believe they knew it was still an issue and still signed it off. With the windows open we turned on the APU bleed again and once again the smell came back. This time sending my First Officer and two flight attendants to the hospital. This also resulted in the cancellation of the flight. When I asked about why they didn't just defer the APU in the first place I heard from someone that the high pressure air cart was broken."




Synopsis: A320 Captain reported a fumes event during pre-flight and had Maintenance take corrective action.  Maintenance worked on it and signed it off as functional; but the crew reported it was still an issue as the smell returned resulting in cancellation of the flight.
Date: 201411
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Cessna 180 Skywagon
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Human-Machine Interface
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Engine failure on short final. Landed in a field just short of the airport. No damage to the airplane or property.




Synopsis: C180 pilot reports an engine failure on short final and a landing short of the field without damage or injury.
Date: 201308
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skylane 182/RG Turbo Skylane/RG
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown; Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: I monitor the CTAF 112.8 for hours at a time and monitor all weather in the region regularly. On almost all occasions at ZZZ airport the sky diving operations pilots use very poor communication; advise area traffic on approach [to] the airport and to remain clear of the area. The general attitude and actions is [that] they do not have to yield to; or accommodate any other traffic at the airport. There is a very distinct 'this is our airport; we do what ever we want; and stay out of our way' attitude. I have personally seen sky dive aircraft take the runway with landing traffic on final with no radio call that they were taking the runway. I have heard the sky diving pilot call out to traffic 'All area traffic do not approach the airport' on multiple occasions insinuating that the airport was closed to all other traffic when in fact it was not. Additionally; they have poor position reporting; do not identify themselves on occasion as a sky dive aircraft; and [do not] use their N number. Additionally; they are very confrontational and combative on the radio.  There is a major issue with procedures and a complete lack of cooperation with other air traffic. I fly all over the country and have never heard or seen such unprofessional and blatant disregard for other traffic and pilots and have never witnessed such improper sky diving operation radio calls. Additionally; I believe that they have access to the ASOS and manipulate the cloud cover reporting function. I believe that they have on several occasions disabled the ceiling and cloud reporting function; so that they can go ahead and jump through solid cloud ceilings. Last time I was there was a solid overcast layer at 5;000 MSL reported all over the region except for the ZZZ airport. When I arrived at the airport it was indeed overcast and they were performing sky diving operations from 14;000 MSL. This was not the first time that this has happened. I firmly believe that they are an accident waiting to happen. Their operations are primarily on the weekends and at the worst possible time due to the amount of low time inexperienced other traffic.




Synopsis: C182 reports poor procedures and communications by skydiving pilots at ZZZ airport on a daily basis.
Date: 201306
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Aircraft component: Pilot Seat
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Human factors: Human-Machine Interface; Situational Awareness
Second reporter function: Pilot Not Flying; Captain
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Rejected Takeoff
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: During the takeoff roll; at approximately 90 to 100 KTS my seat slid back to the full back position. Since I was the pilot flying and could no longer control the aircraft I said 'your aircraft; your aircraft' to the Captain. The Captain took control of the aircraft and rejected the takeoff. In our conversation following the event; the Captain stated that he was unsure of the reason I gave him the controls and that he didn't see my seat slide back; he only heard the 'bang' made by my seat hitting the back stop of the track.Also; during the seat failure; I momentarily pulled back on the flight controls and was unable to maintain directional control with the rudder pedals. The Captain stated that the sound accompanied by the aircraft gyrations caused by the sudden seat shift along with the confusion of being given the aircraft suddenly was what led him to his decision to reject. The reject was uneventful with plenty of stopping margin. We went to a holding area while we confirmed break cooling information and then coordinated a gate return with Operations Maintenance elected to replace my seat.I normally check my seat once I slide it forward for the final time before flight by pushing back against the pedals. For whatever reason this time; it still let go. I probably could have stated more clearly what had happened to help the Captain make a better decision; however; during takeoff there is not much time for a lot of words.


Second narrative: I heard a loud thud; the aircraft then began to rotate (VR 135); and the First Officer stated; 'You have the aircraft.'


Synopsis: The Captain of a B737-700 took control and rejected the takeoff when the First Officer; the original pilot flying was unable to control the aircraft due to a failed seat latch which allowed his seat to slide full aft and he was unable to maintain directional control as a result.
Date: 201812
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: A330
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climb out; we smelled a dirty sock smell. Donned oxygen mask [advised ATC] and decided to return to [departure airport].


Second narrative: Odor/fume of a dirty sock noticed by Captain and First Officer on initial climb out. Oxygen donned by pilots. [Advised ATC] with ZZZ Departure and returned for a landing


Synopsis: A330 flight crew reported returning to their departure airport because of fumes detected on the flight deck.
Date: 202108
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Pressurization Control System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At FL390; pressurization in cabin started to increase. Started a descent and went through the checklist. Shortly afterwards the cabin went to 15;000 feet and O2 masks were deployed. Had requested priority handling with Dispatch and ATC. Alerted FAs (Flight Attendant) of the problem; what to expect. Landed in ZZZ1; intended destination. Debriefed crew; Maintenance; Dispatch; [and] union. Everyone said it was done by textbook procedures.


Second narrative: AT FL390 we were cleared to descend and passing through FL360 we noticed the cabin altitude increasing. We told ATC and initiated an immediate descent. Complied with ECAMs and QRH procedures. Briefed FAs (Flight Attendant) and safely landed aircraft. Debriefed with crew; Maintenance; Dispatch; passengers; and emergency medical support staff.


Synopsis: A320 flight crew reported loss of cabin pressure control and requested priority handling and proceeded to land at destination airport.
Date: 201812
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Toilet Smoke; Overheat; Fire Detectors & Warning
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Time Pressure; Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Other / Unknown; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: About an hour into the flight; during cruise at FL340; had an EICAS lavatory smoke indication. I asked the copilot to get WX/ATIS for the nearest airport and be ready to don the o2 mask. I then transferred aircraft control to him and called the forward cabin inter phone to establish communication with the cabin. The Flight Attendant in the aft galley answered. I started to ask about the situation and the Flight Attendant cut me off and said 'I'm working it!!! I'll call you back' and hung up.I [checked] the clock and quickly reviewed the emergency descent and smoke; fire; or fumes Quick Reference Checklist with the copilot. At 45 seconds elapsed time; I called the forward cabin again to establish communication (if I couldn't; I would assume that the crew was fighting a fire and I would initiate the descent). This time; the Purser and aft galley Flight Attendant answered. The aft Flight Attendant kept talking over the Purser and said that if was a false detection. I thoroughly debriefed them both on crew communication protocol and how very close we came to going to [an alternate].




Synopsis: B757 Captain reported communication breakdown between flight and cabin crew as a result of false lavatory smoke alarm.
Date: 202007
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Flight phase: Parked
Aircraft component: Aircraft Documentation
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Human factors: Distraction
Anomaly: Deviation / Discrepancy - Procedural Maintenance; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Maintenance
When detected: Routine Inspection
Result: General Maintenance Action
Contributing factors: Procedure; Environment - Non Weather Related; Human Factors
Primary problem: Ambiguous

Narrative: Cleaning crew [was] onboard. [I] got distracted by too many cleaning personnel. [The problem was non-compliance with] Fire Bottle Overhaul Due Date.Cleaning crew should be on after interior checks have been completed. Deep cleaning by the cleaning crew lasts longer.




Synopsis: Technician reported being distracted by cleaning crew on board which led to non-compliance with an overhaul due date.