elihoole/asrs-aviation-reports huggingface dataset:
Date: 201606
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Mission: Photo Shoot / Video
Flight phase: Cruise
Airspace: Class G ZZZ
Aircraft component: Throttle/Power Lever
Component problem: Failed
Reporter organization: FBO
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Commercial
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was flying with a photographer when the throttle control stopped responding. I tried to apply more power but it felt like the throttle linkage was damaged/unresponsive. Immediate action was taken to land the Cessna in a field while we still had time to act. The aircraft was about 700 ft AGL when the problem occurred; and we landed in a hay field. Luckily no person was hurt or property damage; also the airplane was not damaged as a result of the incident. The incident was reported to the law enforcement office; and to the nearest mechanic. After inspection it was determined that the throttle cable snapped and that caused the Cessna to lose power.




Synopsis: C172 pilot reported throttle cable issues resulted in a forced landing in a field.
Date: 201904
Local time of day: 1201-1800
Location: DCA.Airport, DC
Flight conditions: VMC
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B DCA; Special Use P56
ATC / advisory: Tower DCA
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Private
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Procedure

Narrative: Captain was flying River Visual to Runway 19 DCA. Washington Tower asked us to square our turn to final. The Captain complied; but it turns out that the aircraft touched P-56. On taxi in; Ground Control asked us to call Potomac Approach. The Captain complied and at the end of the short conversation; Potomac said that the previous two aircraft (different airlines) were asked the same request from Tower and that they too had touched P-56. Two things; have P-56 waypoint as a reference point on NAV display on approach and to get Washington Tower to never issue ATC instructions to square the turn to final Runway 19.




Synopsis: Air carrier First Officer reported a P56 airspace violation after the Control Tower instructed the flight crew to square turn to final while on the RIVER VISUAL RWY 19 to DCA airport.
Date: 201510
Local time of day: 1201-1800
Location: ZAB.ARTCC, NM
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZAB
ATC / advisory: Center ZAB
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Commercial; Flight Crew Flight Engineer
Human factors: Confusion; Situational Awareness
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Exited Penetrated Airspace
Contributing factors: Airspace Structure; Chart Or Publication
Primary problem: Ambiguous

Narrative: I began to fly home. The second leg [I departed] from BVU. I went around the south side of the Grand Canyon attempting to stay out of the Grand Canyon (GCN) Special Flight Rules Area (SFRA). Before leaving home I attempted to find any information I could on this area. I downloaded FAR Part 91 and SFAR 50-2 and studied them and took them with me on my computer. The day before and again the day of the flight I studied SFAR 50-2. The best I could determine was the altitude restrictions and 'Flight Free Zones' in SFAR 50-2 'Section 9. Termination date. Section 1. Applicability; Section 4; Flight-freeze zones; and Section 5. Minimum flight altitudes; expire on April 19; 2001.'There are no altitudes listed on the Las Vegas Sectional. There is no explanation of the GCN SFRA on the Special Use Airspace are of the Sectional margin. I attempted to purchase the Grand Canyon VFR Aeronautical Chart from the FBO at [first leg departure airport]. I landed at BVU specifically to purchase the Grand Canyon Chart from the FBO there. Neither FBO had the chart available. I attempted to find the chart online. The Sectional says to see [FAA website] to find a source for the charts or digital charts. Both these web addresses returned 'error page not found' errors. The floor of the Class E airspace is 9;000 feet on the sectional so 9;500 feet or higher should stay out of the GCN SFRA.While flying South of V210 between GCN and TBC; ABQ Center asked if I was familiar with the GCN SFRA and I replied no as the information is either non-existent or not available. The Center also advised that radar contact was lost and therefore could not help me stay out of the area. I believe I was South of any Special Airspace. I continued on to [destination airport].SFRA 50-2 (As listed on the FAA website) contradicts itself as it says to comply with altitudes in an expired section.




Synopsis: The pilot attempted to avoid the Grand Canyon Special Flight Rules Area but may have entered the southern portion inadvertently.
Date: 201507
Local time of day: 0001-0600
Weather elements / visibility: Turbulence
Light: Daylight
Aircraft: B737-900
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Situational Awareness; Time Pressure
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Attendant
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Weather; Procedure
Primary problem: Weather

Narrative: Turbulence when carts were in the aisle; allowed passenger to sit in jumpseat until safe to move carts and get customer in their seat. No open seats aft of carts to place customer.




Synopsis: A B737-900 Flight Attendant placed a passenger in a flight attendant jumpseat during turbulence when no passenger seats were accessible because of a beverage cart in the aisle.
Date: 202201
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: M-7
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Instructor; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Situational Awareness; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Ground Strike - Aircraft; Ground Event / Encounter Object; Ground Excursion Runway; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; Flight Crew Regained Aircraft Control
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On Date; I was practicing takeoffs and landings with a student that has not flown in 16 months. He had around 100 hours. The winds were straight down the runway at 220 degrees at 11 knots. After the preflight we proceeded to fly in the pattern. I conducted the first pattern and landing. After the first landing he then had complete control of the flight controls. After he conducted the next 3 landings with assistance from myself we then were on final approach for landing and it was a lite chop. While on short final; I commanded a go-around because we are slow and I did not like the unstable approach to land. After I commanded a go around the student got into an elevator trim stall. The plane was stalled and we proceeded to go off the runway with a tail and wing strike. The plane hit a runway light. After getting control of the aircraft I got it back on the runway and stopped.Although I couldn't do much about the stall since it happened so fast I will be more ready for it the next time not only with a low time student pilot who has not flown in 16 months but any other training flight that I will do from now forward.




Synopsis: M-7 flight instructor with student reported an aircraft stall on short final resulting in a tail and wing strike upon landing.
Date: 202106
Local time of day: 0601-1200
Location: ZZZZ.ARTCC, FO
Flight conditions: VMC
Light: Daylight
Aircraft: B747 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Aircraft component: Aircraft Cooling System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport; General Flight Cancelled / Delayed
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Equipment overheat EICAS msg. Followed checklist. Checklist said land at nearest suitable airport.




Synopsis: Captain reported an air turn back caused by an equipment overheat EICAS message.
Date: 201809
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Flight conditions: VMC
Light: Dawn
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Climb
Airspace: Class C ZZZ
ATC / advisory: TRACON ZZZ; Tower ZZZ
Aircraft component: Aileron
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed As Precaution; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On climb out around 3;000 feet with the Captain (CA) flying; the CA stated the ailerons were strange. He asked me to confirm so I took the flight controls and felt at least double the normal aileron force required. CA remained Pilot Flying (PF) for the remainder of the flight. He took a few more turns to assess the feeling; monitored hydraulics and flight controls pages for problems and none were noted. Due to our proximity to [our] destination requiring the visual the CA suggested and I concurred on a diversion. Before proceeding with that; I called up the Flight Attendant (FA) and used the lavatory. Upon return to the cockpit I acquired ATIS; loaded and built the ILS 18L; FA's were advised as I went to the lavatory; I saw an ACARS free text from our dispatcher asking about [our situation]; so I considered the company notified; the Captain briefed a visual and we accomplished the descent check. At some point approach [was notified of our situation.] We were cleared for the visual; the before landing checklist was completed and we landed uneventfully. The CA took the radios for coordination; advised fire/rescue we didn't need assistance or brake check; I accomplished the after landing flow; called ops; acquired [a] gate and proceeded to coordinate with ground for taxi to the gate. Upon arrival at the gate all ops were normal.

Callback: Reporter stated cause was unknown; and the aileron force seemed normal on taxi in.



Synopsis: A CRJ-700 First Officer reported a flight control malfunction with the ailerons.
Date: 201712
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: Mixed
Light: Daylight
Aircraft: B737-700
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: Pressurization Control System
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Time Pressure; Distraction; Human-Machine Interface; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Flight Crew Diverted; Flight Crew Landed in Emergency Condition; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft; Human Factors
Primary problem: Aircraft

Narrative: Cruising at FL400 we heard a loud bang that sounded like it came from the galley. A couple minutes later; the Flight Attendant called and asked us about the noise. At that time; we noticed the cabin altitude climbing. The altitude warning horn sounded shortly thereafter. I told the Flight Attendant we would be landing soon. We proceeded with our immediate action items and notified ATC. Once we were given a clearance to descend; we began an emergency descent. I ran the Cabin Altitude Warning checklist. That checklist led us to the Emergency Descent checklist. We descended the aircraft to below 10;000 ft before taking off our oxygen masks.After descending through 10;000 ft I got a status update from the Flight Attendant. I also briefed them about our diversion and time until landing. I then briefed the Passengers and notified them that they could remove their masks. The First Officer remained the Pilot Flying and did a great job flying and preparing for the landing. We briefed the approach and ran appropriate checklists. As time permitted; we notified Ops. After clearing the runway; we had CFR (Crash Fire Rescue) inspect the aircraft for damage. No visible damage was noted. We taxied to the gate. When we arrived; we had a cabin altitude of approximately 3000 ft. So; I manually depressurized the plane so we could open the door. The aircraft was further inspected by CFR and was deemed secure.




Synopsis: Boeing 737-700 Captain reported loss of pressurization.
Date: 202112
Local time of day: 1801-2400
Location: PHL.Airport, PA
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower PHL
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Distraction; Situational Awareness; Confusion
Anomaly: No Specific Anomaly Occurred Unwanted Situation
Detector: Person Flight Crew
When detected: Taxi
Contributing factors: Procedure; Chart Or Publication; Airport; ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: S2 and S1 labeling signs short of Runway 27L gives the perception that S2 is S1. Move the sign to better location.




Synopsis: Air Carrier Captain taxiing for departure from PHL reported confusing taxiway signage.
Date: 201603
Local time of day: 0001-0600
Location: MDW.Airport, IL
Flight conditions: VMC
Weather elements / visibility: Rain
Light: Night
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: Tower MDW
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Airport
Primary problem: Airport

Narrative: I am writing to communicate a concern I experienced last night regarding braking performance at MDW. I landed on 31C [in] a fairly heavy [large transport aircraft] in wet good conditions; autobrake max; flaps 40 with a headwind of about 8 knots. I touched down approximately 1200 ft down runway; on speed; smooth; no bounce; auto brakes actuated and reverse thrust was applied; normal maximum braking; decelerated for about three seconds until we hit a 'bump' in runway at 4R intersection.We felt main struts extend (but still on ground) and felt aircraft accelerate for approximately one to two seconds; struts then compressed and normal maximum brake deceleration returned. We exited the runway at taxiway Sierra without incident. My concern is the 31C/4R runway intersection elevation difference has become significant and is affecting braking performance.




Synopsis: Air carrier First Officer reported aircraft deceleration on landing was interrupted when a bump was encountered at the intersection of MDW Runways 31C/4R.
Date: 201406
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground ZZZ
Aircraft component: APU
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Workload; Troubleshooting; Physiological - Other
Anomaly: Aircraft Equipment Problem Critical; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: Taxi
Result: Flight Crew Returned To Gate; Flight Crew Took Evasive Action; General Declared Emergency; General Maintenance Action; General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We pushed on time from the gate. We started both engines for the short taxi to the runway. After turning onto Taxiway X from XX; the First Officer smelled electrical smoke in the flight deck. The Captain; then also smelled what he believed to be smoke. Immediately then the Flight Attendant called the flight deck; also smelling electrical smoke. The Flight Attendant indicated the smell was strongest in the rear of the aircraft. We asked Ground Control if we can pull over and look at a problem; Ground asked if we needed assistance. We stated no and will advise.The smoke smell became very strong; making us believe that we were on fire. The First Officer stated that we immediately return to the gate and we were making a 180 on the taxiway. Operations were still at the gate from the push. We then told Ground to roll the trucks. We have no visual indications or aural indications of a fire; however; the cabin was filling with electrical smoke. We parked at Gate X; deplaned all passengers immediately through the main cabin door; leaving all passenger items behind. ARFF examined the cabin and flight deck; they also smelled smoke and began a thermal scan of the flight deck and baggage compartment. ARFF also had no visual indications of a fire; but could smell it. Contract Maintenance then arrived. ARFF needed the aircraft to be pushed away from the gate. The Mechanic and the flight crew then started the process of re-powering the aircraft one system at a time to see if we could determine the cause of the electrical smoke. We then came to starting the APU; after the BIT test the First Officer began the APU start cycle. The airplane started 'clicking' loudly and there was '0' rotation on the APU. I then exited the aircraft and did a visual inspection of the APU; I then noticed all scorching and fire damage to the right side of the aircraft. I took photos and texted them to Maintenance Control.  Cause was APU FAILURE.




Synopsis: During taxi out; both EMB-145 pilots and the Flight Attendant detected a strong cabin odor; so the aircraft returned to the gate and was evacuated. During troubleshooting; a failed APU was found.
Date: 201210
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Cruise
Aircraft component: Circuit Breaker / Fuse / Thermocouple
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Human factors: Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Overcame Equipment Problem
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: The First Officer lifted his backpack which was on the floor behind his seat. His bag strap caught onto the DC Standby Bus CB and there was a momentery power interuption in the DC standby bus. The subsequent result in the power interuption was the loss of the L ENG EEC normal mode. Per checklist and conference with Maintenance; both engines were placed in the EEC ALT MODE resulting in the loss of the autothrottles. Flight continued and landed with no further problems.




Synopsis: B767-300 First Officer's backpack strap caught on and tripped the DC Standby Bus circuit breaker which ultimately resulted in the flight continuing without autothrottles.