elihoole/asrs-aviation-reports huggingface dataset:
Date: 201511
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: Pax Seat
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Relief Pilot
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: I was the IRO on my break. About an hour into my break I smelled smoke and looked up and smoke was coming from seat 3A in front of our rest seat. I pushed the FA call button to alert the flight attendants and got up and asked the passenger to move from the seat. The ISM came over and said she shut off the electric power to the seat. The smell of the smoke was electrical. I opened up the seat to find out where the smoke was coming from. The smoke dissipated fast after power was removed and I felt around for hot spots. I found no real hot spots. The ISM brought over the halon extinguisher and I moved out of the way for her to spray the spot where the smoke was coming from as a precaution. Myself as well as the flight attendants helping all felt around to make sure we felt no heat. After we felt there was no more fire threat I went over to the flight interphone and called the Captain; [who] was on the SATCOM with Dispatch as well as [Maintenance] about the situation. [The Captain] relayed the questions [Maintenance] had to me and I answered their question. [Maintenance] advised to keep the IFE power switch off and felt since the smoke was gone and there was no heat from where the smoke was coming from; we all agreed it was safe to continue. We believed the malfunction was from the seat motor and the threat was over after power was removed from the seat. The Captain was confident that the problem was over [and] asked the rest of the crew if we all felt safe to proceed. We all felt safe to proceed and I asked the flight attendants to continually check the seat area around the seat motor to make sure there was no more heat while the flight continued.




Synopsis: B757 Relief Officer sitting in the cabin noticed smoke coming from another cabin seat. Smoke subsided when power was removed from seat.
Date: 201309
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Light: Daylight
Aircraft: Falcon 2000
Operator: Fractional
Operating under: Part 91
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Fuel Distribution System
Component problem: Malfunctioning
Reporter organization: Fractional
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Training / Qualification; Troubleshooting
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew FLC complied w / Automation / Advisory; Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition; Flight Crew Diverted; General Maintenance Action; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: At FL410 and 1:30 hour into flight crew attempted to balance wing fuel. After fuel was balanced and switches returned to normal position; fuel continued to transfer out of left tank into right tank. Emergency/Abnormal checklist showed two procedures (A & B). Crew selected and completed procedure B of FUEL QUANTITY ASYMMETRY abnormal checklist which was for no fuel leak evident. Fuel continued to reduce on the low side. Crew also noticed that fuel did not increase at a like amount on the high side. X-BP amber warning light remained illuminated contrary to checklist. Crew then suspected both a transfer and a fuel leak problem and completed Emergency/Abnormal Checklist Procedure A which was for fuel leak and called for associated side engine shut down. Left engine was shut down and fuel in left tank stabilized at 2;000 pounds. Emergency was declared and divert to nearest suitable airport was accomplished. Single engine landing accomplished without incident. Initial maintenance inspection found bad fuel transfer valve actuator and multiple fuel leaks in left wing.




Synopsis: A DA-2000 fuel imbalance could not be equalized with normal or emergency procedures so an emergency was declared; the associated engine shut down and the flight diverted where a failed fuel transfer valve along with fuel leaks were discovered.
Date: 201208
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Hydraulic Main System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Shortly after gear up we received an EICAS message L HYD SYS PRESS in addition the status page Indicated RF for the Left Hydraulic System. We determined we had lost all the Left Hydraulic System fluid; I advised ATC of the problem; I declared an emergency and informed ATC we intended to return. I requested the First Officer run the QRH. We secured the Left Hydraulic System as per the checklist. We also advised Dispatch informed the flight attendants and made an announcement to the passengers. I requested one holding turn to run the after takeoff; arrival checklist and review the landing adjustments due to the loss of the Left Hydraulic System. We made a normal ILS approach and landing. We had requested the emergency equipment stand by. I turned the APU on and after we exited the runway ATC requested we stop and wait for the emergency personal to inspect the aircraft. I shut the engines off and kept the brakes off. I was than informed the left landing gear had some smoke that was subsiding coming from around the brakes. The Emergency Personal cleared the aircraft to be towed to the gate.


Second narrative: Turning to 270 heading climbing through about 2;000 FT; noticed caution lights on the EICAS. [We] noticed L HYD SYS PRESS light. Rudder ratio and hydraulic quantity [were] also on. We ran the L HYD SYS PRESS QRH checklist and returned to a landing. Declared an emergency; called CFR and advised Dispatch on ACARS that we were returning. The Captain preformed the landing.


Synopsis: B757 flight crew experiences the loss of the Left Hydraulic System fluid shortly after takeoff. After complying with QRH procedures an emergency is declared and flight returns to departure airport.
Date: 201212
Local time of day: 1201-1800
Location: TEB.Airport, NJ
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Beechjet 400
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class D TEB
ATC / advisory: TRACON N90
Reporter organization: Corporate
Reporter function: First Officer
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Commercial; Flight Crew Multiengine
Human factors: Other / Unknown
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were given the RUUDY 4 departure up to 2;000 FT. I don't believe we crossed WENTZ at 1;500 FT; instead we went straight to 2;000 FT.




Synopsis: Beechjet 400 First Officer reports possibly exceed 1;500 FT on the RUUDY 4 departure from TEB prior to crossing WENTZ.
Date: 201911
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Flight Attendant (On Duty)
Reporter qualification: Flight Attendant Current
Human factors: Physiological - Other
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Crew; Person Flight Attendant; Person Other Person
When detected: Pre-flight
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Prior to boarding our flight there was a sudden and very strong odor that developed very quickly throughout the cabin. All 4 flight attendants and a commuting pilot (pre-board)all smelled the odor similar to what I relate to fuel or hydraulic fumes.  I went quickly to inform the Captain in the flight deck and immediately all 4 Flight Attendants and commuting pilot deplaned on to the jetway. Our lead Flight Attendant felt dizzy and my throat and eyes were burning. At that time; the passenger agent opened the door leading from the terminal to the jetway to begin boarding and she immediately started waving her hand in front of her face and asked us what the awful smell was.  Those of us on the jetway didn't even realize that the fumes were still around us so we proceeded to exit the jetway into the terminal. The agent delayed boarding and called to report the incident.  Our Lead Flight Attendant called flight daily ops to report it as well. Maybe it was 20 minutes before the fumes dissipated and the cabin crew went back on the aircraft to begin boarding for the flight.




Synopsis: A321 Flight Attendant reported very strong fumes during preflight. Maintenance action required a delay to dissipate fumes.
Date: 201901
Local time of day: 0601-1200
Location: ZSE.ARTCC, WA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Beechcraft / Beech Aircraft Corp Undifferentiated or Other Model
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Cruise
Airspace: Class E ZSE
ATC / advisory: Center ZSE
Reporter organization: Air Taxi
Reporter function: Captain; Single Pilot
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Bird / Animal
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented; Flight Crew Took Evasive Action; Flight Crew Returned To Clearance
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Environment - Non Weather Related

Narrative: While flying at 11;000 feet on an IFR flight plan on V23 approximately 30 miles south of BTG VOR; I found myself converging on a very large area of many flocks of migrating geese. I made a turn to the left keeping my eye out and on the flocks watching all of them as they passed off the right side of the aircraft inadvertently turning 30 degrees as ATC indicated. I was contacted by ATC of the deviation and realized in my attempt to divert from the geese; I inadvertently flew off course resulting in a deviation of the flight planned clearance route. Upon notification from ATC; I resumed navigation back to V23 keeping an eye to the sky for more geese. The rest of the flight was uneventful.




Synopsis: BE-99 pilot reported a track heading deviation after an evasive maneuver to avoid a flock of birds near BTG VOR.
Date: 201210
Local time of day: 0001-0600
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Mission: Passenger
Aircraft component: Hydraulic Main System
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Automation Aircraft Other Automation; Person Flight Crew
When detected: In-flight
Result: Flight Crew Diverted; Flight Crew Landed in Emergency Condition; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon gear retraction; ECAM message received for loss of Green Hydraulic system. TOW weight was about 166;000 pounds. Declared emergency; diverted to [nearest suitable airport] due to long runway; and unlimited visibility. Gravity extended gear; landed overweight approximately 156;000 pounds. Uneventful landing. Tow in to the gate due to no nose wheel steering.




Synopsis: A320 First Officer reported loss of Green Hydraulic System upon gear retraction. Flight diverted to nearest suitable airport featuring a long runway and good weather.
Date: 201312
Local time of day: 1201-1800
Location: CSG.Airport, GA
Flight conditions: VMC
Light: Daylight
Aircraft: RV-7
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class E A80
ATC / advisory: TRACON A80
Aircraft component: GPS & Other Satellite Navigation
Component problem: Improperly Operated; Design
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Engineer; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness; Human-Machine Interface
Anomaly: Airspace Violation All Types
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Human Factors; Aircraft; Airspace Structure; Chart Or Publication
Primary problem: Human Factors

Narrative: VFR direct flight took us northbound just east of Columbus; GA at 8;500 MSL. Approaching Class D/R3002 airspace (Lawson AAF MOA) I checked current altitude restrictions on our dual GPS moving map system with satellite XM NOTAM updates; and another system with active ADS-B information. My Dynon SkyView system showed active restricted airspace from 8;000-14;000 MSL and from surface to 4;000 FT. We descended to 7;500 FT to avoid these areas; but did not realize that a third layer of restrictions was active between 4;000 and 8;000 MSL. The moving map display made it difficult to discern all three layers of the active restricted airspace (R3002 A; B; C). After the flight I discussed the error with Atlanta TRACON. In hindsight; I should have either avoided the MOA altogether; or have been in VHF contact with Columbus ATC before passing through the area.




Synopsis: RV-7 pilot reports inadvertent entry into R3002 due inability to see the individual A; B; C areas of R3002 on his moving map display. R3002B was active.
Date: 201812
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Aircraft: No Aircraft
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Routine Inspection
Result: General Work Refused
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While security screening of passengers baggage the TSA staff found 2 containers of Glass Cleaner.




Synopsis: Load personnel reported TSA found Hazmat cleaning solution in passenger baggage.
Date: 202103
Local time of day: 1201-1800
Aircraft: A300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Pre-flight; Routine Inspection
Result: Aircraft Equipment Problem Dissipated; Flight Crew Overcame Equipment Problem; General Maintenance Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Hazmat can improperly built (loaded) Class 4.3 which requires separation from Class 8. Both of these class shipments were present and did not have required separation. These items were actually right next to each other. All of the Hazmat items were secured under a net. (First Officer) FO noticed lack of required separation and brought to attention of ramp agent. Ramp agent arranged items correctly and re-secured the net. Improper Hazmat can buildup (loaded).




Synopsis: A-300 Captain reported Hazmat shipment incorrectly loaded. Flight crew had Hazmat cargo reconfigured in accordance to Hazmat regulations prior to departure.
Date: 201412
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Rain; 3
Light: Daylight
Aircraft: Golden Eagle 421
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ; Tower ZZZ
Aircraft component: Reciprocating Engine Assembly
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Multiengine
Human factors: Troubleshooting
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Returned To Departure Airport; Flight Crew Inflight Shutdown
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: Communicated with tower for takeoff instructions and cleared to takeoff. After takeoff; tower instructed pilot to contact Center and report back to tower. Problems with initial communications with ATC due to HF not functioning properly and then going to the use of a satellite phone. By the time communication [is] established with Center; tower was no longer within communication range. [Soon after]; plane developed engine trouble and the right engine was shut down and feathered in accordance with the emergency checklist. Fuel to the right engine was stopped. The pilot elected to return to departure point rather than proceed to destination. The rest of the flight was conducted on the left engine and a single engine VFR landing was made. Oceanic flights should be allowed to use satellite phones for communications rather than HF radios or at least the pilots should be given a choice.




Synopsis: C421 pilot reports difficulty contacting Center using an HF radio after departing on an overwater flight and believes that pilots should have the option of using a satellite phone. Less than an hour after after takeoff an engine problem develops and the right engine is shut down and the flight returns single engine to the departure point.
Date: 201905
Local time of day: 0601-1200
Location: SNA.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
Airspace: Class C SNA
ATC / advisory: Tower SNA
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Distraction
Second reporter function: Pilot Flying; First Officer
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Procedure
Primary problem: Aircraft

Narrative: SNA Tower advised us holding short Runway 20R that we would be given an expedited takeoff after landing traffic. After position and hold clearance; SNA Tower clears helicopter on north ramp for takeoff and then also clears us for takeoff.I initially couldn't see the helicopter because of the center windscreen divider; but after 60 knots I picked up the helicopter gaining altitude about half way down runway just north of our intended track. My guess was helicopter came within 500 feet laterally and at our altitude of 200 ft. As we approached V1 speed; I mentioned to flying FO (First Officer) to look out for the helicopter. We continued on course without evasive action; but this event at this airport is unsatisfactory for 121 aircraft and performance runway issues. At altitude we both agreed this was very uncomfortable spacing and we have no formal training for low altitude separation maneuvering.


Second narrative: We were cleared to line up and wait on 20R after a landing [traffic]. Tower cleared a helicopter to take off from the Northwest pad followed by clearing us for takeoff without delay due to a GA jet on final. During takeoff I noted the helicopter lifting off in uncomfortably close proximity to our right wing. While there was no collision or perceived immediate need to maneuver; we were uncomfortable with the helicopters proximity during our rotation. If the helicopter were to drift towards us we would be required to maneuver at low level toward a closely spaced GA Runway. At cruise; we evaluated the taxi diagram and scale and observed that both west side helicopter pads are within 500' of aircraft taking off of Runway 20R. Traffic avoidance of helicopters while taking off of a short runway is an unnecessary threat which can cause loss of control on takeoff; rejected takeoff followed by possible over run or collision with the helicopter or other GA aircraft on the smaller runway.


Synopsis: A319 flight crew reported a near mid-air collision with a helicopter during take-off.