elihoole/asrs-aviation-reports huggingface dataset:
Date: 201211
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Flight conditions: VMC
Aircraft: Dash 8-200
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Aircraft component: Fuel Tank
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Fuel Issue
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Landed in Emergency Condition; Flight Crew Inflight Shutdown; Flight Crew Returned To Departure Airport; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: While climbing through 13;000 FT; I noticed the Number 1 fuel system appeared abnormally split. Knowing that I had been fueled accurately; I immediately looked to the Number 1 wing. I noticed a mist/vapor being expelled from what appeared to be the magnastick location. I am uncertain of where the actual leak was. I had advised the First Officer that we would be declaring an emergency; which we did and turned back. Due to this unique situation; we had looked for a specific emergency checklist but none existed. We had approximately 4;500 LBS at the time we noticed the issue. We then proceeded to shut down the Number 1 engine as a precaution; via the SOP and emergency checklist. We returned; landed; and taxied off the runway. I had requested from that point that we be towed to a safe location. An entry was made in the aircraft logbook.


Second narrative: After departure; during the initial climb to 14;000 FT; the Captain noticed a fuel imbalance. The Captain then noticed fuel leaking overboard from the left wing. The Captain called for a 'fuel leak' checklist. No such checklist existed. The Captain elected to declare an emergency with ATC and return. The Captain then exercised emergency authority and the crew shut down the Number 1 engine using memory action items as a precaution. The Captain then called for the Engine Failure/Fire Checklist. The checklist was followed to the end and the crew landed safely.


Synopsis: DHC8-200 flight crew notes a fuel imbalance during climb and sees what he believes is a fuel leak on the left wing. The left engine is shut down and the flight returns to the departure airport.
Date: 201404
Local time of day: 1201-1800
Location: ZTL.ARTCC, GA
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Personal
Flight phase: Cruise
Airspace: Class A ZTL
ATC / advisory: Center ZTL
Reporter organization: Personal
Reporter function: Captain; Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Private
Human factors: Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Procedure
Primary problem: Procedure

Narrative: Controller directed me to descend to FL230 from FL250 then switched me to another Controller. I checked in with the new Controller and let him know I was leaving 250 for 230. He acknowledged my check in. Then called out traffic. I looked for traffic; but could not see it until it passed under my left wing and then saw it. I informed the Controller I had the traffic. I then noticed it was pretty close. As I was about to radio the Controller the other pilot asked if I was descending. The Controller immediately canceled my clearance and moved me back to 240. I executed his command. I do not know for sure; but the other pilot said my aircraft came within 500 FT of his.




Synopsis: A single engine pilot was cleared to FL230 from FL250 and during descent traffic was called out which he did not see until it passed beneath him less than 500 FT. ATC recleared the pilot to FL240.
Date: 202007
Local time of day: 1201-1800
Location: ZZZ.Airport, us
Flight conditions: VMC
Light: Daylight
Aircraft: MD-11
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Takeoff / Launch
Airspace: Class B ZZZ
Aircraft component: Engine Air Anti-Ice
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
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 Returned To Departure Airport; Flight Crew Inflight Shutdown; General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: After takeoff at approximately 2000 feet; ENG 2 A-ICE Duct illuminated. Followed QRH procedures. Shut down number 2 engine. Returned to ZZZ. Landed uneventfully.




Synopsis: Captain reported an inflight shutdown and an air turnback due to an anti ice advisory light illuminating.
Date: 201511
Local time of day: 0001-0600
Location: ZKC.ARTCC, KS
Flight conditions: VMC
Weather elements / visibility: Turbulence
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZKC
ATC / advisory: Center ZKC
Aircraft component: Hydraulic Main System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; Flight Crew FLC complied w / Automation / Advisory; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: We were at cruise at FL350. When doing the level off checks; the CA noted that there was lower than normal Yellow Hydraulic Fluid Quantity.We continued flight and [enroute] we received an ECAM alert 'LOW YELLOW HYDRAULIC PRESSURE.' We followed the ECAM and turned off the associated pumps; referenced the QRH and [flight manual] and made the decision to continue. [Later] we got 'LOW YELLOW HYDRAULIC QUANTITY.' We then ran the ECAM and reviewed once again the QRH and [flight manual]. Looking at the associated system failures; we determined that on landing we would be unable to get off the runway without assistance. At that point; we received no land ASAP message and made the [decision] to continue to [our destination]. We then informed ATC of the malfunction; requesting services to help us to vacate the runway and requesting the longest runway due to the malfunctions. We landed uneventfully and were escorted off the runway by operations and a super tug.




Synopsis: A320 FO reported continuing to destination after loss of Yellow Hydraulic System.
Date: 201511
Local time of day: 1201-1800
Location: NCT.TRACON, CA
Flight conditions: IMC
Weather elements / visibility: 7
Light: Daylight
Aircraft: Large Transport
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E NCT
ATC / advisory: TRACON NCT
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Distraction; Situational Awareness
Second reporter function: First Officer; Pilot Flying
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Climbing on TECKY2 approximately 4;000 feet given climb unrestricted clearance to FL190 expedite through 7;000 feet. Aircraft given full power to approximately 3;500 feet VSI climb rate. Passing through 4;800 feet clearance cancelled to maintain 5;000 feet. Response to ATC was 'leveling 5;300 feet returning to 5;000 feet.' Our return to 5;000 feet was a bit slow and ATC prompted to return to 5;000 feet quickly.TCAS traffic was visible on and to west at 6;000 feet; but no TA or RA.  I don't recall exactly due to heavy radio traffic and MCP adjustments; but our course may have been approximately .5 miles west as magenta line randomly shifted during our turn on procedure possibly causing NorCal to cancel climb; but we were not notified of that.  NorCal then reissued the exact same clearance passing abeam traffic at 6;000 feet. Flight continued uneventfully.


Second narrative: On the TECKY2 Departure from SJC; I initiated a 30 degree right hand turn from MLPTS; but noticed I was tracking inside of the magenta line; so rolled out to approximately a 15 degree banked turn to match the magenta line and the white one minute airplane track line (as well as the flight director in LNAV). ATC issued a climb and requested we expedite through 7;000 feet. The Pilot Monitoring deleted the reduced climb thrust and we began to expedite the climb. About half-way through the turn the screen refreshed and the magenta line all of a sudden was well inside the turn. I returned to 30 degrees of bank. At approximately the same time ATC told us to level at 5;000 feet. When I looked at the altimeter we were passing 5;000 feet; so I initiated an immediate level-off; reaching approximately 5;400 feet. I then initiated a slow descent to 5;000 feet. After approximately a minute; we were once again given the climb with a request to expedite through 7;000 feet. We continued the SID and climbed normally.


Synopsis: While departing SJC on the TECKY2 Departure; the crew received an expedite climb clearance which was shortly followed by an immediate level-off clearance. There was TCAS traffic in the vicinity; but no TA was received.
Date: 201807
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Skyhawk 172/Cutlass 172
Operator: FBO
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Initial Climb
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Engine
Component problem: Failed
Reporter organization: FBO
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Commercial; Flight Crew Flight Instructor; Flight Crew Multiengine; Flight Crew Instrument
Human factors: Time Pressure
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Landed in Emergency Condition; Flight Crew Inflight Shutdown; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Returned To Departure Airport
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: On takeoff on runway ZZ at around 350 ft AGL; I experienced loss of power on my engine. I was instructing a primary student on a flight. I told the tower that I was having engine problems and needed to land. ATC cleared me to land on runway ZY. I pitched for best glide speed and turned towards the runway. I tried emergency procedures for restart with fuel; magneto; and mixture and there was no restart. I did the Engine Failure /Power Loss During Flight checklist for landing with no engine power and glided to landing. I told the tower we needed to be towed to the maintenance hangar.Not aware of what caused the situation or what could be done to fix it.




Synopsis: Cessna 172 flight instructor reported an engine failure after takeoff.
Date: 202104
Local time of day: 1201-1800
Location: MMFR.ARTCC, FO
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
ATC / advisory: Center MMFR
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine; Flight Crew Instrument
Human factors: Confusion; Troubleshooting; Situational Awareness
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Chart Or Publication; Human Factors; Procedure; Airspace Structure
Primary problem: Procedure

Narrative: Descending into MMPR on the OBRUG 1B. Told to descend to FL200. Then told to descend via as we were passing FL260. There's a discrepancy between the FMC which loads to 'Cross OBRUB at or above 230;' and the chart which says 'Cross at 230.' Once given the initial descent to 200; I deleted the FMC (at or above 230) and crossed above 230 even though told to descend via. Which is correct? The chart or the FMC; and in Mexico was I supposed to cross OBRUG at 230 (as per the chart) even though initially cleared to 200 (and only later) at 260; given the descend via




Synopsis: Air carrier Captain reported procedure disagreements between the FMC and the chart exist on the PVR OBRUG 1B Arrival.
Date: 201407
Local time of day: 0601-1200
Location: LRD.Airport, TX
Flight conditions: VMC
Light: Daylight
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 135
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Landing
Airspace: Class D LRD
ATC / advisory: Tower LRD
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Multiengine
Human factors: Distraction; Situational Awareness; Communication Breakdown; Confusion
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action; Flight Crew Rejected Takeoff
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: While landing at LRD on Runway 17R; just after touchdown; Tower cleared another aircraft that was holding in position on Runway 14 for takeoff; which crosses 17R approximately halfway down the runway. We had yet to cross Runway 14 on our landing roll and were very concerned that the departing aircraft and our airplane would reach the intersection at the same time. We called on Tower frequency and alerted them to our position and that we were not yet clear of Runway 14. I immediately applied brake pressure and came to a stop just before the hold short line for 14. The other aircraft also aborted takeoff. Once we were sure the other aircraft was stopped; Tower cleared us to continue across Runway 14; and the rest of the taxi was completed uneventfully.




Synopsis: Pilot reports while landing and before his aircraft had passed an intersecting runway; Tower Controller clears an aircraft for takeoff. Landing pilot slams on brakes and stops before intersection. Pilot advised Tower while stopping and departing aircraft rejected takeoff.
Date: 201207
Location: HEF.Airport, VA
Aircraft: No Aircraft
Reporter organization: Personal
Reporter function: Pilot Not Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Communication Breakdown
Anomaly: No Specific Anomaly Occurred All Types
Detector: Person Flight Crew
When detected: Pre-flight
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings
Primary problem: ATC Equipment / Nav Facility / Buildings

Narrative: Can you get the phone AWOS back on line at Manassas (HEF)? This is so critical to pilots that fly in and out of the airport. I am based there with an aircraft in the hangar. The phone is the fastest and easiest way to get quick information; trends; and changing conditions. It would be a great help to all that fly to/from this airport.

Callback: The reporter provided no additional information other than advising the AWOS continues out of service.



Synopsis: An HEF based pilot is distressed that the HEF specific AWOS has been out of service for an extended period.
Date: 201411
Location: ZZZ.Airport, US
Weather elements / visibility: Rain
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Ramp
Human factors: Situational Awareness
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors; Weather
Primary problem: Ambiguous

Narrative: On my walk around I found icing on the backside of the fan blades and leading edge of fan blades. I told the push driver and the manger that was standing there about it and that I had 17 years of deicing and felt that the engine should be cleared of contamination. The manager looked at it and said it could go but I believe he was worried about just getting it out due to multiple planes waiting for gates.




Synopsis: Ground personnel reports discovering ice on the back side of the fan blades during his walk around inspection and reporting it to his manager. The manager takes a look and does not believe it is significant and the aircraft is allowed to depart.
Date: 201511
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: EMB ERJ 145 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Training / Qualification; Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural Hazardous Material Violation; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural FAR; Inflight Event / Encounter Other / Unknown
Detector: Person Ground Personnel
When detected: Aircraft In Service At Gate
Result: Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Procedure; Manuals; Company Policy
Primary problem: Procedure

Narrative: Our cargo load report on departure indicated that there was 26 pounds of 'freight' in the cargo bin. No description of the freight was on the cargo report; and none of the items at the bottom had been circled. Upon arrival at [destination]; ramp personnel notified me that unauthorized hazardous material had been loaded onto the aircraft. I inspected the box and found it was extremely well labeled.Near the packing slip was a sticker: 'PRIMARY LITHIUM BATTERIES- FORBIDDEN FOR TRANSPORT ABOARD PASSENGER AIRCRAFT' On every side of the box was placed a bright orange sticker with the words: 'CARGO AIRCRAFT ONLY FORBIDDEN IN PASSENGER AIRCRAFT.' I never did open the box to verify the contents. I have pictures of the cargo report and the box with all stickers visible if needed.It is currently not our procedure to go into the cargo bin and verify hazardous material or claims of freight. Although not very practical; that would be one solution to the problem.


Second narrative: [Report Narrative Contained No Additional Information.]


Synopsis: An EMB-145 crew was notified after arrival that a 26 pound Lithium-Ion battery shipment had been transported even though clearly labeled 'CARGO AIRCRAFT ONLY FORBIDDEN IN PASSENGER AIRCRAFT'.
Date: 201812
Aircraft: B737 Undifferentiated or Other Model
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
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown; Ground Event / Encounter Other / Unknown
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General None Reported / Taken
Contributing factors: Procedure
Primary problem: Procedure

Narrative: The pilots have a procedure when the 737 aircraft terminated at a station to turn off the batteries. This leaves the cabin crew deplaning with pax without the use of the interphone or PA in the event of an emergency.




Synopsis: B737 Flight Attendant reported dangerous situation during deplaning at trip termination due to ground power interruption.
Date: 201310
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Captain
Human factors: Communication Breakdown; Training / Qualification
Second reporter function: First Officer
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Flight Crew Returned To Gate
Contributing factors: Airport; Human Factors; Procedure
Primary problem: Ambiguous

Narrative: Normal marshaling into gate; stopped normally; normal hand signals to include chocks in signal from Marshaller. At that point I released the parking brake and called for the Parking Checklist. While accomplishing the checklist; I notice movement in my left peripheral vision; glanced up; saw the jetway moving forward; smoothly applied brakes; and set the parking brake. The aircraft started rolling backward and either pushed the rear chock out of place; the chock was incorrectly positioned; or not in position.  Rampers came on the intercom; hooked up the tow bar; and towed the aircraft forward to the stop point; and I set the parking brake for the remainder of the turn. There was a briefing page change which I reviewed before reporting to the aircraft and reviewed it once again enroute. I overlooked the notice to keep parking brakes set at [specific gates at this airport; including the one we wereparked at]. A more vigilant review of the briefing page on my part would have prevented this. Recommend that briefing pages with gates like this have the gate list include bold lettering to draw additional attention to special gate requirements.


Second narrative: Parked at Gate XXX; Ramper gave us the chocks in signal. Captain released the parking brake and we began the Parking Checklist. After a few seconds; the Captain noticed the aircraft was rolling backward. He quickly set the parking brake and the aircraft stopped. We communicated with the Rampers via headset and they pulled us back into the gate. More vigilance by the Ground Crew giving hand signals at an appropriate time. More vigilance for the flight crew during times when we are heads down accomplishing checklists.


Synopsis: B737 flight crew reports rolling back after parking at the gate with chocks in. The brakes are applied and the ground crew tugs the aircraft back to the spot. The company briefing page indicates that at this gate and another the company uses at this airport require the parking brakes to remain set at all times.