elihoole/asrs-aviation-reports huggingface dataset:
Date: 202003
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Hazardous Material Violation
Detector: Person Flight Crew
When detected: Pre-flight
Result: Flight Crew Overcame Equipment Problem; General Maintenance Action; General Work Refused
Contributing factors: Manuals; Human Factors
Primary problem: Manuals

Narrative: At departure time; CA (Captain) was informed of DG (Dangerous Goods) in one of the pits. Crew received no paperwork regarding the DG. [manifest] did not indicate any DG. CA called Dispatch and I called Load Planning. Load Planning said that the package was blood labeled UN3373 and that it did not require pilot notification. CA wanted to see some kind of reference for this. Dispatch then conferenced the DG hotline with CA. DG hotline rep said that it was not fully regulated but was not very clear or confident about it with the crew. Crew then refused the items rather than take further delay. This is the second flight in a couple months that I have had that took delays due to DG that are not 'Not-Fully Regulated Shipping Handling Codes'. Crewmembers are unaware of this type of labeling and hear 'Dangerous Goods' and want paperwork or something that shows them they are acting according to procedure. I talked to the Duty Manager and he was also unaware of any DG that don't require pilot notification. During my research; I spent a long time trying unsuccessfully to find the IATA/ICAO Dangerous Goods Manual that is referenced in [the manual]. Load Planning Supervisor was finally able to point me in the direction of a 'Dangerous Goods Briefing' put out by the safety department. This briefing document talks about Not-Fully Regulated SHC (Shipping Handling Codes) and how they should be handled. I have attached it. It provides the necessary information but would not be easily accessible to crews.




Synopsis: Airline Dispatcher reported flight crew refused to transport Dangerous Goods that did not require flight crew notification. FOM directs flight crew to be provided Hazmat documentation when transporting Dangerous Goods.
Date: 201906
Local time of day: 0601-1200
Location: DAB.TRACON, FL
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class E DAB
ATC / advisory: TRACON DAB
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Air Traffic Control Separated Traffic
Contributing factors: Company Policy; Human Factors; Airspace Structure
Primary problem: Company Policy

Narrative: Aircraft X departing SFB northbound and was deviating east around a weather cell through the DED jump zone. The skydive aircraft was on the ground after a jump. The skydive [aircraft] is supposed to follow the jumpers to pattern altitude so we know they are safe. Aircraft X wanted to turn to the left back into the weather because he said he saw the jumpers barely below him at 8;000. My trainee gave Aircraft X a hard right turn to a 080 heading to keep south and east of the jumpers.The LOA states that the skydive [aircraft] is supposed to follow the jumpers so we know when they are on the ground. There has been multiple accidents/incidents with the jump zone and no one seems to care about the safety of commercial flights because of skydive. It's a horrible spot there is so much land to the west that would be better. They have caused problems with aircraft inbound to DAB when we are on east operations. Something needs to be done. The skydives never stay in the area they are supposed to. They have climbed close to aircraft when they climb north through the final. It's very dangerous and it needs to be looked into!!!




Synopsis: DAB TRACON Controller reported an air carrier needed to deviate off course to avoid skydivers who were not in compliance with their Letter of Agreement.
Date: 201907
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: IMC
Weather elements / visibility: Rain; Turbulence; 5
Light: Daylight
Aircraft: Super King Air 300
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class E ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Instructor; Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Loss Of Aircraft Control; Inflight Event / Encounter Weather / Turbulence
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control; Flight Crew Returned To Clearance
Contributing factors: Weather
Primary problem: Weather

Narrative: I departed ZZZ and was climbing to 6;000 feet. I encountered moderate turbulence and up-drafts. Before I could regain control; I was 500 feet off my assigned altitude. I regained control and descended back to 6;000 feet.




Synopsis: Pilot reported that turbulence and updrafts caused loss of aircraft control and altitude deviation.
Date: 201910
Light: Daylight
Aircraft: B777-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Lifevest/Jacket
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Powerplant; Maintenance Airframe
Human factors: Communication Breakdown; Confusion
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Maintenance; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Attendant
When detected: Aircraft In Service At Gate
Result: General Flight Cancelled / Delayed; General Maintenance Action
Contributing factors: Procedure; Company Policy; Aircraft
Primary problem: Company Policy

Narrative: A log page was created at departure time about life vests found on the aircraft galley counter.After speaking to the inflight crew; they had found 2 life vests on the mid galley counter. 1 still had the pull strap attached; so it would not be part of the spare kit.I consulted my supervisor; who then consulted Maintenance Control. The passengers would have to come off the aircraft to allow us to perform an inspection to determine which seat/seats were missing life vests. My supervisor spoke to the Captain along with the Purser; they were in agreement.The purser was about to make the announcement to the passengers; only to be interrupted by an Inflight Supervisor to tell the purser to stop.My supervisor announced himself and the situation to the Inflight manager. The manager then stated that social media determined this to be unacceptable; the passengers will check for the missing life vests; we are not taking them off.My supervisor demanded the passengers off the aircraft so maintenance can perform the necessary inspections. The Captain was in agreement and the passengers were then deplaning.My shift ended so I had to leave; I do not know the outcome of this.Having the passengers perform a safety inspection is unethical and possibly illegal. The life vest pouches are sealed; and this is a safety risk as well. For as long as I have worked for the company; I have never had been ordered to perform maintenance in this type of manner. How can a social media team order aircraft maintenance?




Synopsis: Technician reported that two life vests were found in the aircraft galley during boarding and resulted in a flight delay so that an inspection can be performed.
Date: 201712
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Parked
Aircraft component: Engine Drain Mast
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Other / Unknown
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Ground Personnel; Person Other Person
When detected: Aircraft In Service At Gate
Result: General Maintenance Action
Contributing factors: Aircraft; Company Policy
Primary problem: Company Policy

Narrative: It has come to my attention that the 737 pilots are being told to not write up engine leaks and to push off the gate and start the leaking engine and let the gate crew determine if the engine stopped leaking. This by passes a wide range of Maintenance Manual and other procedures. Aircraft X pushed off the gate the Captain requested the ground crew that pushed off determine if the engine stopped leaking they refused the Aircraft ground interrupted and came back to the gate were it was properly trouble shot and returned to service. A quote out of the B737 operating states 'If a fluid leak (other than a continuous stream) from any of the engine drains is discovered during the Exterior Inspection; the engine can be started.'I as an Aircraft Mechanic I have a hard time believing that someone untrained and who did not follow Maintenance Manual procedures is able to determine what type of fluid is leaking and were it is leaking from and what the leak limits are. A lot of times the only way to determine what drain is leaking is to open the engine cowls.' As required by 14 CFR 121.563 all discrepancies discovered by the flight crew shall be entered in the Aircraft Maintenance Logbook (AML) by the flight crew.' There are a lot of dangerous situations that can occur by not checking out a fluid leak endangering both passengers and flight crews; ground crews and Maintenance crews by starting a leaking engine.




Synopsis: Ground operations employee reported that Boeing 737 flight crews are told not to write up engine leaks.
Date: 201812
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Light: Daylight
Aircraft: Cheetah; Tiger; Traveler AA5 Series
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class G ZZZ
Second aircraft: Small Aircraft
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Commercial
Human factors: Communication Breakdown
Anomaly: Aircraft Equipment Problem Less Severe; Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Aircraft
Primary problem: Ambiguous

Narrative: On doing a touch-and-go landing; I noticed another aircraft on short final to the opposite runway. As I lifted off the runway I altered course to the right and the other aircraft landed to a full stop. I called on the CTAF and asked if the other aircraft was on the frequency; and got no reply at the time. As I was turning downwind for a full stop landing; I heard the pilot of the other aircraft call and offer an apology for not having his radio on the correct frequency. I landed and taxied to the ramp where the other aircraft was waiting. The other pilot stated; via radio; that he had had a radio malfunction. Radio transmissions from the other aircraft contained static but were understandable. The other pilot stated that he could hear me fine. Upon initial approach to the airport; I had called on the CTAF at 10 miles out and then at 5 miles out; announcing my intentions for a touch and go on Runway XX. I also called again in the traffic pattern announcing my turns. I heard no other radio transmissions on the CTAF until the call from the other pilot when I was on downwind for my second landing; as mentioned above.




Synopsis: GA pilot reported a NMAC with an aircraft landing opposite direction with radio problems at a non-towered airport.
Date: 201306
Local time of day: 0601-1200
Location: CLT.Airport, NC
Light: Daylight
Aircraft: Dash 8-300
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Takeoff / Launch
ATC / advisory: Tower CLT
Aircraft component: Turbine Engine
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: Other Takeoff roll
Result: Flight Crew Rejected Takeoff
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Aircraft failed to meet takeoff power; left engine only able 70% torque.




Synopsis: A DHC-8 flight crew rejected their takeoff due to low torque on the left engine.
Date: 201705
Local time of day: 1201-1800
Location: FRG.Airport, NY
Flight conditions: VMC
Light: Daylight
Aircraft: Challenger 300
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class D FRG
ATC / advisory: Tower FRG
Second aircraft: Cessna Single Piston Undifferentiated or Other Model
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Conflict Airborne Conflict
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were cleared for a visual approach to Runway 14.  While turning base to final; we encountered a head-on with a single engine Cessna. We received an RA and made an evasive maneuver to miss the Cessna. We then continued our approach and landed without further incident.




Synopsis: CL300 Captain reported a TCAS RA with a single engine Cessna while turning base to final for Runway 14 at FRG. Evasive action was taken by the Captain and the approach continued to landing.
Date: 201701
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: PA-28R Cherokee Arrow All Series
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Aircraft component: Gear Down Lock
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Private
Anomaly: Aircraft Equipment Problem Critical; Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Right main gear collapsed on landing. The gear never locked into position. Everything possible was done to get the gear to lock. The landing had little damage to aircraft and no injuries.

Callback: A mechanical failure caused the gear to fail to lock in the down position.



Synopsis: PA28R pilot experienced a failure of the right main gear to lock in position when extended. After landing the gear collapsed.
Date: 201401
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Night
Aircraft: EMB ERJ 170/175 ER/LR
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; Captain
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Flight Crew
When detected: In-flight
Result: Flight Crew Returned To Clearance; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: While performing a night visual approach into XXXX in VMC conditions; we received an EGPWS warning. We were on the XXXX arrival. When we reached XXX waypoint we were instructed to fly 270 heading and descend and maintain 9;200 feet. Approach Control then asked if we had the airport in sight; we replied yes and were cleared for the visual approach. I then turned the airplane to an approximately NNW heading to set up for a left base. While on the left base we received an EGPWS warning; 'caution terrain.' As a result I began to shallow my descent. We then received an EGPWS warning 'pull up.' I called go-around and executed the EGPWS recovery maneuver. The autopilot was off at the time; I disengaged the autothrottle; applied fire wall thrust; [and] kept the wings level and pitched up. I then proceeded to make a left hand turn towards the airport. Immediately the warnings went away. I still had the airport in sight and visually confirmed that were clear of terrain; so we reestablished ourselves on final approach and landed normally.We picked the runway due to its longer length and because the winds were from the west. We didn't choose to land on one of the east runways because that would have given us a tailwind on landing. Reviewing the event; I think landing on one of the other runways with an instrument approach procedure could have been a better choice even if would have given us a tailwind.


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


Synopsis: During a night visual approach to a runway with nearby high terrain an EMB175 crew responded to a 'caution Terrain' followed by an EGPWS 'pull up' warning. The warnings ceased immediately once the escape maneuver was initiated; and the visual approach was reestablished and continued to a successful landing.
Date: 201903
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness; Distraction; Time Pressure; Training / Qualification
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Illness / Injury
Detector: Person Flight Crew
When detected: Taxi
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Taxiing out of the alley approaching taxiway an employee bus ran the stop sign at full speed and appeared not to see our aircraft. I slammed on the brakes and came to an abrupt stop and so did the bus. The whole bus was in our taxiway and the closest point of approach was 20 to 30 feet. The driver put the shuttle in reverse and backed up to the stop line and I continued to taxi. We notified ground control and I checked on the cabin crew. The number 1 Flight Attendant told me they were OK but that the number 3 had been in the forward lavatory and sustained a bruise on her arm. I asked if they were okay to continue and she said yes. After arrival; the number 1 Flight Attendant also said she bruised her arm on the forward galley counter. I asked them both to fill out a report.Remind shuttle drivers not to be involved in distracted driving.




Synopsis: B737 Captain reported a near collision on ground with shuttle bus which did not yield to aircraft taxiing.
Date: 201201
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Aircraft: Amateur/Home Built/Experimental
Operator: Personal
Operating under: Part 91
Flight plan: VFR
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Reporter organization: Government
Reporter function: Local; Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: I was working Local Control/CIC position. I was looking at my runways when I noticed a general aviation aircraft taxiing across Runway XXL at Bravo. I interrupted the conversation going on between the Ground Controller and Flight Data and stated; 'which one of you is talking to that aircraft!'; and I pointed to the plane that was now in between the parallels. I attempted to reach out to the aircraft on my frequencies. The Ground Controller attempted to do the same. After reviewing the tapes (Ground Control); it was discovered that the pilot read back the correct runway assignment. I feel that the two controllers should have played a more vigilant role in LOOKING OUT the window. We had a similar event; same scenario happen earlier this month. I feel if there had been less socializing and more attention to aircraft this event could have possibly been prevented. Recommendations: Perhaps we need better signage at the intersection; it is in fact a hot spot at our airfield. Maybe a warning sign could be displayed at the intersection. Pilots need to pay attention to runway environment or ask controllers for assistance if they are uncertain. Less socializing; controllers need to do their job and maintain vigilance by looking out the window because situations can occur at any level or volume of traffic. Encourage higher standards of personal professionalism of controllers for the sake of safety.




Synopsis: Tower Local/CIC noted an unauthorized runway crossing missed by others in the Tower; the reporter listing a number of corrective actions that might prevent future occurrences.