elihoole/asrs-aviation-reports huggingface dataset:
Date: 201311
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Takeoff / Launch
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty); Flight Attendant In Charge
Reporter qualification: Flight Attendant Current
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: About 3 minutes after wheels up I saw smoke in the AFT of the cabin. Right when I saw the smoke coming out from under the seats I got out of my jumpseat pushed the emergency button advised the flight deck that I had smoke filling the cabin then hung up.  [I then] stowed my jumpseat; got the Halon 1211 and PBE and went back to where smoke was coming out from under the seats. Upon running to where the smoke was coming from I saw that smoke [had] started coming from under the seats in not only the AFT of the aircraft; but now MID aircraft. I then got down in the aisle moved passenger's small carry on items that were under their seats out of the way and started looking for the cause of the smoke and feeling with the back of my hands for hot spots on the fuselage just in case it happened to be a hidden fire. After not being able to feel any heat and the smoke got so thick I got back up as the flight deck was calling me to check on the passenger's; myself; and condition of the cabin and also advising that we would be landing very shortly. I then advised them that it started to clear out a little bit from what I could see. I then had passenger's advising me that they could smell burning rubber and wood. Due to not seeing any flames I did not use the Halon 1211 or the PBE. I then took my jumpseat as we were close to the ground and preparing for landing. When we made it safely on the ground fire trucks met the aircraft on the runway to inspect it. We then taxied to the gate and deplaned the passenger's and awaited an aircraft to be ferried for us to continue on to our destination. Reason for the event is unknown I was never told exactly what the smoke was from other than the things they thought it was.




Synopsis: CRJ200 Flight Attendant describes a cabin smoke event about three minutes after takeoff and the subsequent return to the departure airport.
Date: 201408
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Strobe Light
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying
Human factors: Physiological - Other; Human-Machine Interface
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: The strobes on this aircraft are still flashing inside the cockpit when it gets dark out. In addition they are so bright that when the pilot looks out to scan for traffic they blind you; forcing you to turn them off. Just when I'm sure that the Airbus Corporation and their product couldn't set the bar lower; they do with their apathetic attitude to this clear safety issue. I have personally submitted a couple of safety reports on this and nothing has happened. This situation causes potential pilot vertigo. It destroys night vision. It forces me to turn off a lighting system; thereby making my aircraft less visible. And Airbus; with their arrogance; apparently could not care or less. I absolutely cannot believe that they are not being required to fix this. Unbelievable. Airbus [should] man-up; drop the arrogance; and fix their awful designs.




Synopsis: An A320 pilot reported the aircraft's strobe light system is poorly designed and located and constitutes a safety hazard by compromising flight crew vision.
Date: 201202
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: Aeronca Champion
Flight plan: VFR
Flight phase: Initial Climb
ATC / advisory: Tower ZZZ
Second aircraft: Cessna Aircraft Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Communication Breakdown
Anomaly: ATC Issue All Types; Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
Result: Air Traffic Control Issued New Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Cessna was on right base cleared to land Runway 25R; I heard a Champ call for a left crosswind departure from Runway 25L; I cleared the Champ for departure from Runway 25L approving the left crosswind departure. I noticed the Champ departing Runway 25R ; I sent the Cessna around; the Champ stopped his takeoff roll; I then cleared the Champ for an intersection departure from Runway 25R.




Synopsis: Tower Controller described a potential conflict event between traffic cleared to land Runway 25R and traffic cleared off Runway 25L; but in fact was initiating a departure from Runway 25R that resulted in a go around and an aborted takeoff.
Date: 201708
Location: ZZZ.Airport, US
Weather elements / visibility: 10
Aircraft: Skyhawk 172/Cutlass 172
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Engine
Component problem: Malfunctioning
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Diverted; Flight Crew Landed As Precaution
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were cleared for takeoff [and] were assigned to fly 3000 feet heading 150. Just before reaching 3000 feet; we got cleared to climb to 5000 feet heading 240. Just before reaching 5000 feet we heard a loud pop from the engine followed by an RPM drop of about 500 RPM. It took a moment for the engine to regain its normal RPM (perhaps 2 seconds). My crew partner and I talked to each other to see if either of us knew what just had happened. As we concluded that we didn't know the reason for the pop and RPM drop; we requested to divert back to [a nearby airport] to be cautious. Departure asked if we would like emergency [handling]. We responded saying that our engine is running fine now and verified by referencing all engine instruments. Departure directed us to [the nearby airport] and declared [on] our behalf an emergency to give us priority. To conclude; we decided it was safer to turn around and fly back to have our plane examined. As we landed a fire fighter truck and the police was waiting for us and making sure that we arrived safely.




Synopsis: C172 pilot reported diverting to an alternate airport after hearing a 'pop' and noticing an RPM drop.
Date: 201305
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
ATC / advisory: Ramp ZZZ
Aircraft component: Nose Gear Tire
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Confusion
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Vehicle
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Procedure; Equipment / Tooling
Primary problem: Ambiguous

Narrative: We flew what we thought was a normal flight. We parked and shutdown the aircraft. As the agent moved the jetway a large bang was heard. My immediate thought was that the jetway had struck the airplane; however the Ramp Agent told me that my nose tires had exploded. Not really sure what that meant; I went downstairs to look at the tires. I saw two slices on each tire; horizontally across the tire; looking toward the tire from the front. The top slice was not that severe; but the bottom slice was large enough to cut into the sidewall and ran the width of the tire. The Ramp Agent suggested that the electro tug could slice the tires if the leading edge of the metal lip was too sharp. We departed from the previous airport and they used a similar tug to push us back. I noticed no abnormal nosewheel issues during taxi out; takeoff; landing; and taxi in. I have no idea what happened for sure; but I reported the discrepancy to Maintenance. I have a photo that I attached.We rely on the ground staff to properly service our airplane. If they make an error; it is understood that they will notify the crew to properly have it serviced. If the damage to the nosewheel did in fact happen at the previous airport; the whole flight (unknowingly to us) was unsafe.




Synopsis: After gate arrival following a normal flight; the nose tires exploded and upon examination two large horizontal cuts were discovered across the tire possibly caused by the previous airport's pushback tug.
Date: 202111
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Light: Daylight
Aircraft: Bombardier Learjet Undifferentiated or Other Model
Operator: Government
Operating under: Part 91
Flight plan: IFR
Flight phase: Descent
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Communication Breakdown; Situational Awareness; Workload
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Ground Event / Encounter Ground Equipment Issue; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Airspace Structure; Chart Or Publication; Equipment / Tooling; Human Factors; Procedure
Primary problem: Airspace Structure

Narrative: Flight check was on an IFR flight plan and asked to test the MSAW (Minimum Safe Altitude Warning). He was issued a descent to 1700 ft. and headed toward a 2000 ft. MVA (Minimum Vectoring Altitude) for an antenna. Flight check never set the MSAW off and descended below 1700 ft. to 1500 ft.. I issued a vector to a 340 heading to avoid the obstruction MVA and just registered his descent as an anomaly since he was requesting to try and cause the alarm. In the process of telling flight check he wasn't setting the alarm off and answering other questions. I didn't realize he read back the wrong heading and then flight check cancelled IFR but had already entered the MVA of 2000 ft. at 1700 ft.More transparency with the flight check aircraft and the pilot should have been VFR when descending below the MVA in an intentional attempt to set off the MSAW system.




Synopsis: TRACON Controller reported an aircraft descended below their assigned altitude; read back the wrong heading assignment; and flew below the Minimum Vectoring Altitude. The ATC Minimum Safe Altitude Warning never activated.
Date: 202012
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Other / Unknown; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors; Company Policy; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: Passengers were sitting in seats across from the jump-seat. There was not 6 feet between us. We were face-to-face! Our knees were touching. I'm concerned about the safety of not socially distancing between Crew jump-seats and passenger seating.




Synopsis: Flight Attendant reported there is not enough room to social distance between the FA jump-seat and passenger seats.
Date: 201707
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: clear
Light: Daylight
Aircraft: Seaplane or Amphibian
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: Other landing roll
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After landing on [the] lake for the third or fourth time; the airplane went through a sudden deceleration and stopped with the left wing low. I could see that the left wing float brace was broken which allowed the wing float to swing outboard up to the wing. Upon power up; the airplane could be leveled however it failed to come up on the step for takeoff. Airplane took on water faster than the bilge pump could expel and the plane started sinking. Could not make it to targeted beaching point so I took airplane to nearest shoreline which was lined with mangroves; dropped the landing gear and there it sat partially submerged until recovered. While heading for shore; I transmitted several times my name; location; and that I was taking on water and losing directional control and to contact my friend and tell him I needed help. Too much going on and ambient noise so I did not hear any response. ELT was also going off in my headset and could not be reset with front panel control/indicator. Later inspection revealed that all three rubber hull boots had failed and allowed water to enter the hull evidently faster than the bilge pump could expel.




Synopsis: Sea Rey LSX pilot reported the aircraft partially sank after taking on water related to the failure of the rubber hull boots.
Date: 201511
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Weather elements / visibility: 5
Light: Daylight
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Oil Cooler
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Workload
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Zero oil quantity indicated on engine Number 2 on climb out. Indication was steady; and temperature was climbing and pressure was falling. Captain retarded throttle to see if indications would change and they did not. Performed engine oil quality low or decreasing non alert checklist. It directs you to the engine shutdown checklist. We completed that procedure. We dumped approximately 70;000 LBS of fuel in that same general area at 17;000. Returned to [departure airport] uneventfully. It was later told to us by maintenance that the fuel/oil heat exchanger had ruptured; sending fuel into the oil case in the engine.




Synopsis: An MD-11 crew shut down engine in flight because of loss of oil after a fuel/oil cooler ruptured followed by fuel dump and returned to the departure airport.
Date: 202001
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: Citation X (C750)
Operator: Fractional
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Fractional
Reporter function: Pilot Not Flying; Captain
Human factors: Communication Breakdown; Situational Awareness; Fatigue
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Second leg of day. Flying from ZZZ to ZZZ1. Pilot Flying was FO (First Officer); I was the Pilot Monitoring although the Captain. Weather was VMC. ZZZ1 was landing RWY XXL utilizing RNAV XX Z. We flew the approach utilizing RNAV procedures; Vertical Speed; with altitude settings set for each altitude restriction. All altitude restrictions and procedures were briefed according to standard briefing card.  Prior reaching the final approach fix at 2;400 ft.; we set the LNAV MDA for the approach which was 1;020. Upon reaching the FAF; we began our descent to the MDA looking toward ZZZZZ as the MAP. Upon arriving at MDA; the runway was clear in visual sight approximately 4 NM; the flying pilot concentrated on maintaining the final approach course which is offset by 11 degrees. Ride was light to moderate turbulence. We never went below MDA. At this point; we were given a low altitude alert by Tower; we acknowledged this radio call and climbed higher above MDA. We were then given our landing clearance behind a B737; and landed with no further issues. Upon review on ground of our FMS waypoints; we only saw loaded ZZZZZ1; ZZZZZ2; ZZZZZ. Upon review of the approach plate; we then noted ZZZZZ3 (a fix inside the FAF) which had a altitude restriction of 1;240 which is 1.6 NM from MAP and 2.9 NM from Runway XX. Although we briefed that restriction at cruise altitude; during the business of the ZZZ airspace arrival; traffic; and busy; gusty approach; we both mistakenly utilized the loaded FMS waypoints. Not having ZZZZZ3 in our FMS provided us a false assumption we could come down directly to the MDA. This is what drew the low altitude alert from Tower I believe. Again; we were also VMC with my eyes outside ensuring we could also line up with runway.In my opinion; we simply missed this altitude restriction at ZZZZZ3. Despite out best efforts to brief and understand the GPS approach; we failed to remember this during the actual approach. We also failed to back ourselves up by perhaps placing this additional fix into the FMS. I could have also chose to use VNAV knowing the weather. This was the second flight of the day; at end of a day at night - rolling fatigue was a probable issue as well.




Synopsis: Citation pilot reported the stepdown fix inside the Final Approach Fix was not entered in the FMS; which resulted in missing the stepdown altitude restriction and ATC issuing a low altitude alert.
Date: 201201
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: Mixed
Weather elements / visibility: 5
Light: Daylight
Aircraft: Cessna 150
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Workload; Training / Qualification; Situational Awareness; Distraction; Confusion
Anomaly: Inflight Event / Encounter VFR In IMC; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed As Precaution; Flight Crew Became Reoriented
Contributing factors: Weather; Human Factors
Primary problem: Ambiguous

Narrative: Returning from short flight I suddenly encountered low clouds and [there] appeared to be instrument conditions ahead. Attempting to land at an alternate airport; I found the runway closed for an event. Making another 180 I found myself in instrument conditions; total white out. Remembering 'fly the plane' I decided to go higher and also noticed wings not level. I got that straightened out and kept climbing slowly. I was listening to CTAF for my destination. I radioed that I had a problem; Instrument Meteorology Conditions. The young lady in a minute or so got an experienced pilot on the radio. He questioned where I was; altitude; etc.; and suggested that I was; indeed; heading correctly. He said AWOS was showing >800 FT and suggested I descend slowly. After a few minutes the ground was visible; my heading to airport was correct so I made a very long base; then final and landed safely. Prior to flight I received complete briefing and during that briefing the Briefer and I decided to change my planned flight due to potential IMC conditions. The shorter; along the coast flight should have been clear according to forecast. The next day I got an instructor to review what I had done and suggest improvements.




Synopsis: A VFR C150 pilot received a preflight weather brief and changed his flight path but upon return to his departure airport he became IMC. With verbal assistance from another pilot he was able to descend below the clouds and safely land.
Date: 201604
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Dash 8-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Aileron Trim System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: During climbout the FO experienced a gradual left wing down tendency. He attempted to counter this with RWD trim. Upon clicking RWD on the aileron trim the trim went to full LWD. Attempts to move it to the RWD position were not successful and the EA checklist for Runaway Aileron Trim was accomplished. We notified ATC immediately that we would like to stop the climb at 5;000 to run checklist and may return to the field. The EA checklist was completed however the situation remained. The FO was able to with right control force hold wings level with some effort. We adjusted the speed through a range of speeds to ensure the plane would be controllable at low level low speed and determined that the condition was not made worse with a reduction of airspeed. We however felt that it would be unsafe to continue to fly for 40 minutes to burn enough gas to land below max landing weight. The flight attendant was notified that though we would be arriving in an emergency state; we were anticipating a normal landing and an evacuation was not foreseeable. We informed the passengers of the same thing.  During the landing roll; the FO set the plane down smoothly and brakes were lightly used as the plane was slowing safely without them.




Synopsis: Dash 8 Captain reported experiencing a runaway aileron trim malfunction. The flight returned to the departure airport after unsuccessful troubleshooting.