elihoole/asrs-aviation-reports huggingface dataset:
Date: 201509
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PA-46 Malibu/Malibu Mirage/Malibu Matrix
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Second aircraft: Piper Aircraft Corp Undifferentiated or Other Model
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument
Human factors: Distraction; Situational Awareness; Workload
Anomaly: Aircraft Equipment Problem Less Severe; Conflict NMAC
Detector: Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: Leaving ZZZ runway 22L in use. Given choice of right or left turn out by ground control. Chose right turn since it was less intrusive to the pattern of 22L. Given takeoff clearance from 22L by controller after line up and wait instruction. Advised by controller to fly straight out and right turn outside of other aircraft; which was an Archer on the departure end; in flight. Take off was uneventful initially. However the landing gear malfunctioned and would not completely raise or lower. I advised tower that I had a landing gear issue. I maintained heading for a few more seconds. On about the fourth cycle the gear lights; normal thump of gear tucking away and pump was noted. The controller asked if I wanted to return to the airport. I replied negative; since it was now functional. At this time I was rapidly closing on Class Bravo airspace. My reaction was to turn to avoid Class Bravo with purpose; since I did not have an emergency issue or clearance. I turned right; as this was my given instruction. I then realized I did not confirm visual identification of the other aircraft before turning. I started a climb and the traffic system gave me a warning. I briefly saw what I thought was the traffic after the warning. The controller asked if I had seen the traffic. I responded yes; but now am not certain that I did ever see the other airplane.This incident could have been prevented if I had asked for an amended departure after the gear problem occurred; instead of continuing to cycle the gear in a confined departure environment. I could have asked for a left turn instead of simply following the instructions with a plane on my right.




Synopsis: A PA-46 pilot reported a NMAC in the vicinity of the departure airport when he was distracted by a landing gear problem.
Date: 202101
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Rain
Light: Dawn
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Cowling/Nacelle Fasteners; Latches
Component problem: Improperly Operated
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: Time Pressure
Second reporter function: Pilot Flying; Captain
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: Other Post Flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: We discussed as a crew that in the future when we get pressured by time constraints and environmental pressures (i.e. raining hard during the walk around) that we won't allow ourselves to be hurried and in a rush. That is when things get missed.I missed the cowl latch key left in the Number One Engine on the preflight walk around. It was dark and raining hard and we were running a little bit late due to an excessively long line at the KCM (Known Crewmember) checkpoint.


Second narrative: We discussed as a crew that in the future give us more time to get to the airplane in ZZZ with the long train ride and busy departure time. And no matter never get caught rushing any procedure. Get down on your knees and check those cowl keys! Long line at KCM (Known Crewmember) Checkpoint and we were rushing to get the flight out on time. Rainy cloudy morning in ZZZ FO (First Officer) missed cowl latch key during walk around. Proper keys and pins located on the [Aircraft] during our interior cockpit preflight. Only informed of our mistake by the outbound crew in ZZZ1. Captain called Crew Scheduling to get my number.


Synopsis: Flight Crew reported being informed that they missed the cowling door latch key still installed in the engine cowl latch and departed.
Date: 201508
Local time of day: 0601-1200
Location: ZBW.ARTCC, NH
Weather elements / visibility: Rain
Light: Daylight
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZBW
ATC / advisory: Center ZBW
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Troubleshooting; Confusion; Distraction
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Procedure; Weather; Airspace Structure
Primary problem: Weather

Narrative: Moderate to severe precipitation were causing deviations within 50 miles of Boston airport. Arrivals were being rerouted back over KRANN intersection to fly the ROBUC 1 and the 22 L transition on a trial basis as the weather was moving out and they would be able to pick their way through. A few minutes after the first two airplanes were vectored in deviating around weather I was told to go into a hold for Boston. Approximately 4 planes were given holding instructions over PROVI. After doing one turn in holding I was told to run them radar using descend via to runway 15R which was a different runway than the originally had. The first aircraft was Aircraft X and I told him to turn right direct KRANN and descend via the ROBUC 1 15R transition. He would have not been able to make the turn to PROVI to pick up the arrival because it would have been too tight of a turn. He reads it back but tells me a few seconds later that KRANN is past the transition point and he would like to go direct JOODY. At that time I had a few BOS departures and was vectoring others out of the hold and did not have a chance to pull up the Arrival in the URET. I approved his request to go direct JOODY and descend via. I say him leave [at] 110 before he got to PROVI but assumed that BOS approach had that airspace. It was not till minutes later that the CIC (Controller in Charge) informed me that I had an airspace violation with PVD approach because there is not a crossing altitude at JOODY so he descended too early to stay out of their airspace. Because descend via is still rather new and some runways get used a lot more than others it is still confusing as to which transition and fix to go to after deviations or holding. During deviations or coming out of a hold descend via should be cancelled so that as airplanes go off course and ask to vectored back on there is no confusion over what speed and altitude to maintain from either pilot or controller.




Synopsis: ZBW Controller reports of deviations due to weather and precipitation with traffic inbound to BOS. Controller let aircraft descend early and assumed BOS had the airspace; but ended up violating airspace belonging to Providence Approach.
Date: 202011
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Air Conditioning and Pressurization Pack
Component problem: Malfunctioning
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Maintenance; Flight Deck / Cabin / Aircraft Event Illness / Injury; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Passenger
When detected: Pre-flight
Result: General Evacuated; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was the B FA (Flight Attendant) on Aircraft X. We had finished boarding. I was near the aft section of the cabin. I heard a passenger ask 'is that normal?'. There was then smoke coming from the back rows air vents. Smoke was quickly filling the cabin and the fumes were extremely strong. It was burning my nose and throat. I called the A and told him what was going on and to notify the pilots. It was getting harder to breathe and see. We decided to have passengers get off the aircraft for safety. I was getting very light headed; I went back to get the C FA and make sure no passengers were left behind. After everyone got off; the C and I did not feel well at all. We asked to have an EMT look at us. My heart rate was extremely high and blood pressure was high from my normal. We received oxygen. A supervisor met up with us and said she could smell the fumes coming off from us because it was so strong. We still felt very dizzy; lightheaded; my throat was sore and I felt pressure in the back of my head. We decided it wasn't safe for us to continue with our trip due to the exposure. I got further medical attention later at a hospital due to my throat feeling worse. Earlier our water lines were frozen. The mechanics were attempting to fix the frozen line and this all occurred.We also have a video that can prove how thick the smoke was




Synopsis: B737-700 Flight Attendant reported smoke emitting from air vents during boarding resulted in cabin crew experiencing health issues accompanied by passenger complaints. Passengers were deplaned and maintenance was requested.
Date: 201203
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Shortly after gear retraction the left engine began to have compressor stalls. The throttle was retarded and the stalls stopped. I informed ATC that we were returning to the field and declaring an emergency. I requested the men and equipment to standby. The First Officer and I discussed our options and possibilities. I briefed the flight attendants about our situation and made a PA to the passengers informing them we were returning to the airport due to an engine problem. The First Officer and I briefed the approach and decided to use flaps 28 in case of an engine failure. After completing checklists we landed overweight. The landing was smooth and I shut down the left engine after stopping on the runway. I elected to remain on the runway until we were inspected by the Fire Department. After we were informed of no fire or visible damage we taxied to the gate and deplaned without further incident.




Synopsis: An MD-83 flight crew declared an emergency and returned to their departure airport without incident after experiencing compressor stalls from the left engine shortly after takeoff.
Date: 202012
Local time of day: 1201-1800
Location: CRP.TRACON, TX
Aircraft: Medium Transport; High Wing; 2 Turboprop Eng
Operating under: Part 91
Flight plan: VFR
Mission: Other unknown
Flight phase: Cruise
Airspace: Class E ZHU
ATC / advisory: TRACON CRP
Second aircraft: King Air C90 E90
Reporter organization: Government
Reporter function: Approach; Instructor
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Training / Qualification; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Automation Aircraft TA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Training on North radar; Aircraft X a VFR CN35 at 065 just maneuvering about 15miles south of the CRP airport. Aircraft Y; IFR at 060 flying southbound underneath the CN35. No traffic restriction was given to the CN35 nor was traffic issued to either aircraft. About 7 minutes later the Aircraft X wants to report a near midair and says he had to respond to a TCAS hit for traffic. There was no other traffic close to the Aircraft X so it had to be the Aircraft Y at 060 who he was referencing. Too much confidence in the trainee led me to not ensure the traffic was issued. Take action and instruct trainee to issue traffic or restriction when you see the situation.




Synopsis: ATC Instructor reported that while giving training; a traffic call was never issued; following that one of the two aircraft reported a near miss.
Date: 201603
Local time of day: 0001-0600
Location: ZZZ.Airport, US
Weather elements / visibility: Thunderstorm; Turbulence
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Speed All Types; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Weather
Primary problem: Weather

Narrative: Event was caused by unexpected turbulence and inability to maintain airspeed at altitude.While enroute to ZZZ we encountered a patch of severe turbulence in an embedded storm. However very little was showing on the radar and there were no prior reports of anything more than moderate chop. Our speed slowly began dropping off; I increased power and requested a descent to FL360. We leveled off there but still could not maintain speed; I requested to descend again to FL340 and increased to Takeoff power. At some point in the descent we got the stick shaker very briefly. We executed SOP procedures and recovered uneventfully. All passengers and flight attendants were seated and no injuries were sustained. Initiate more power and quicker descent faster.




Synopsis: CRJ-700 First Officer reported speed dropped off enough in severe turbulence to trigger a momentary stick shaker at FL360.
Date: 201404
Local time of day: 1201-1800
Location: ZZZ.Tower, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: DA20-C1 Eclipse
Operator: Other Flight School
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Powerplant Lubrication System
Component problem: Malfunctioning
Reporter organization: Other Flight School
Reporter qualification: Flight Crew Multiengine; Flight Crew Commercial; Flight Crew Instrument
Human factors: Other / Unknown
Second reporter function: Instructor
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Departure Airport; Flight Crew Landed in Emergency Condition; Flight Crew Took Evasive Action; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon initial climbout from the Class D airspace we experienced engine roughness coupled with a red line oil temperature and no oil pressure indication on the engine gauges. In order to preserve the safety of flight we declared an emergency and returned the aircraft to the airport via left traffic into Runway XX.  There were no issues discovered in preflight and the aircraft had just been flown prior.  A run up check was done before receiving takeoff clearance and no issues were discovered.  All engine instruments were in the green and the engine ran smoothly.  Takeoff and initial climbout had no issues and we were cleared for an Instrument Departure from Runway XX.  Once established in the climb the engine started to run rough while the temperature gauge pegged max temperature and oil pressure dropped to zero. At this time we declared an emergency and turned back to the runway for landing.


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


Synopsis: A DA-20 began running rough after takeoff while the oil temperature increased to maximum and oil pressure decrease to zero; so an emergency was declared; a turn made to the nearest runway; and a safe landing completed.
Date: 202105
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Aircraft component: Exterior Pax/Crew Door
Component problem: Malfunctioning
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 Critical; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: I have written the main cabin door on this airplane up four times. The Flight Attendant can't open it with anywhere close to normal force. I had the First Officer and Flight Attendant film the force required to open the door and they couldn't do it. It only opened after I put IMMENSE force on the handle. My hunch the entire time has been that the door gets stuck once we pressurize to high altitude cabin differential of around 7.5 PSID. This is a safety hazard because the door is the primary exit in the event of an emergency. Of the four times this door was forced open after it was written up; two of the write-ups were done with our own aircraft maintenance personnel on board and two I personally forced the door open with almost all of my strength and leverage.The airplane should be ferry flown to a maintenance base and undergo flight testing to determine what is causing the main cabin door to jam itself shut after flight.




Synopsis: Captain reported that the Flight Attendant could not open the main entry door and had written the door up four times with no corrective action.
Date: 201308
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Galley Furnishing
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Deviation - Speed All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Approximately 18 minutes into the flight at around FL240; an emergency call was made by the Flight Attendant. She indicated there was a fire in the galley area and [to] immediately land the airplane. We contacted Center to declare an emergency. I commenced to execute an emergency descent and turn back. We were told there was a field by us; but the runway was considered marginal in length. The First Officer and I donned masks and had goggles ready if needed. We could smell the burning electrical wiring. The Flight Attendant contacted us again and indicated that she put the fire out with the halon but the cabin was smoky. We elected to release the passenger oxygen masks to aid in breathing if the fire returned. We were cleared to the departure airport where we made a normal approach and landed. We were able to taxi to the ramp where ARFF personnel were standing by. Evaluation of the coffee machine was made and determined the fire originated there. Initially in the descent; exceeded the speed of aircraft by excessive descent. Reduced the pitch and brought the aircraft back to satisfactory descent profile. Otherwise; I believe the crew acted quickly and effectively to capture and contain the threat. The Flight Attendant performed her job in an outstanding manner and the First Officer was effective and precise in handling the tasks needed to allow me to focus on flying the airplane and bring back to [departure airport] safely.




Synopsis: EMB-145 Captain is informed of a fire in the galley by the Flight Attendant during climb. An emergency descent is initiated during which an overspeed occurs and the flight returns to the departure airport after hearing that the fire is out.