Regional jet in near-collision with Pilatus PC-12 after runway incursion at Charlotte

The U.S. National Transportation Safety Board (NTSB) is investigating a runway incursion that caused a near-collision several days ago at Charlotte Douglas International Airport (CLT), North Carolina. A PSA Airlines regional jet and a general aviation turboprop aircraft were involved in the incident, which occurred at about 10:17 AM on May 29, 2009. No one was injured.

At the time of the incident, a PSA Airlines CRJ-200 regional jet, operating as US Airways Express Flight 2390, was preparing to depart CLT for a scheduled passenger flight to Craven County Regional Airport, New Bern, NC (EWN). According to information released today by the NTSB, the jet was cleared for takeoff on runway 18L.

As the CRJ began its takeoff roll, a privately operated Pilatus PC-12 single engine turboprop aircraft was cleared to taxi into position and hold farther down the same runway in preparation for a departure roll that was to begin at the taxiway A intersection.

After the ground-based collision warning system (ASDE-X) alerted controllers to the runway incursion, the takeoff clearance for the regional jet was canceled. The jet rejected takeoff.

The pilot of the turboprop, seeing the regional jet coming down the runway on a collision course, taxied the PC-12 to the side of the runway. The FAA reported from the scene that the regional jet stopped approximately 10 feet from the PC-12.

On board the CRJ were three crew members and 42 passengers. The number on board the PC-12 was not mentioned, but the NTSB notes that there were no injuries reported among those on board either aircraft.

According to the NTSB, visual meteorological conditions prevailed with 9 miles visibility.

Update on the Allentown airport runway near-collision in September

Th U.S. National Transportation Safety Board (NTSB) has issued an update on the near-collision between a regional jet and a small general aviation aircraft at Lehigh Valley International Airport, Allentown, PA, this past September. The update includes a time line of events, and a photo (at right) of the tire marks made by the jet as it swerved to avoid a collision with the smaller aircraft.

Readers will recall that on the evening of September 19, 2008, a Canadair CRJ-700 aircraft (registration N506MJ), operating as Mesa Air Shuttle Flight 7138, was preparing to depart Lehigh Valley International Airport (ABE) for a scheduled passenger service to Chicago. The CRJ aborted take off from runway 6 at ABE due to what the NTSB has classified as a runway incursion. According to factual information provided by the NTSB, the CRJ rejected takeoff at a speed of about 120 knots (138 mph), skidding around a Cessna R172K (registration N736GV) that had just landed and was still taxiing on the runway. The crew of the CRJ estimated the distance between the two aircraft as 10 feet when they passed.

The CRJ had four crew members and 56 passengers on board; the Cessna was carrying a pilot and two passengers. No injuries were reported, and neither aircraft was damaged.

Today the NTSB released an advisory that included the following timeline of the near-collision incident:

7:29:28 - Cessna contacts Allentown tower while about 8 miles east of the airport.

7:33:30 - Cessna, in landing pattern for runway, is cleared to land on runway 6.

7:34:50 - Mesa Air regional jet contacts tower and reports ready for takeoff and holding short of runway 6. Controller instructs pilot to hold short of runway 6 for landing traffic.

7:36:15 - Cessna crosses threshold of runway 6 and lands.

7:36:27 - Mesa Air instructed by tower controller to taxi into position on runway 6 and hold.

7:36:36 - Tower controller asks pilot of Cessna where he intends to park. Following pilot response, controller provides taxi directions, instructing pilot to exit runway
at taxiway A4.

7:37:11 - Mesa Air cleared for takeoff.

7:37:18 to 7:37:32 - Controller turns attention to an inbound aircraft and issues landing instructions.

7:37:34 - Cessna pilot informs tower controller that he had missed the A4 taxiway and asks for permission to exit at taxiway B.

7:37:42 - Controller replies, "...no delay, turn immediately," which Cessna pilot acknowledges.

7:38:16 - Mesa Air radios tower controller: "We got it, tower - we're going to need to go back to the gate."

Following the incident, both aircraft taxied to parking. The Mesa Air crew elected to cancel the flight and have the aircraft inspected. The Cessna taxied to general aviation parking and concluded the flight.

Today's report included the photo above, showing tire marks created on the left side of the centerline by the Mesa Air regional jet as it veered around the Cessna.

NTSB investigators have interviewed the pilots involved in the incident, and the air traffic controllers on duty at the time of the incident as well as the FAA tower managers. To date, the NTSB has released factual information about the incident, but has not issued a final report that includes probable cause.

It should be noted that the National Air Traffic Controllers Association (NATCA) issued a statement claiming that the control tower at ABE was staffed by unsupervised trainees at the time of this incident. NATCA suggests that at least part of the blame for this serious runway incursion incident lies with the control tower staffing policies of Federal Aviation Administration (FAA).

[Photo Source]

Near-collision between a Mesa Airlines regional jet and a Cessna 172

The U.S. National Transportation Safety Board (NTSB) is investigating a near-collision this past Friday, Sep. 19, 2008,  between a Mesa Airlines Canadair Regional Jet CRJ-700 carrying 60 people, and a Cessna 172 aircraft. The incident, classified by the NTSB as a runway incursion, occurred on the evening of September 19, 2008, on a runway at Lehigh Valley International Airport (ABE), Allentown, PA. No one was injured, but it apparently was a very close call.

According to information supplied by the NTSB, a Cessna R172K (registration N736GV) was on a landing roll on runway 6 at the Lehigh Valley International Airport when the pilot was instructed to exit the runway at taxiway A4. Mesa Airlines flight 7138, a CRJ-700 (registration N506MJ), already instructed to position and hold on the same runway, was then given clearance by the same controller to take off.

During the takeoff roll, the Mesa crew heard the Cessna pilot say that he had missed the taxiway A4 turnoff and ask to exit at taxiway B. The Mesa crew saw the Cessna ahead of them on the runway and aborted the takeoff at about 120 knots, swerving around the Cessna. The Mesa crew estimated that they missed colliding with the Cessna by about 10 feet.

Night visual meteorological conditions prevailed at the time of the incident.

NTSB investigating runway incursion at Fresno, CA

The U.S. National Transportation Safety Board (NTSB) is investigating the circumstances surrounding a runway incursion incident yesterday, Aug. 28, 2008, at Fresno Yosemite International Airport (FAT). The incident involved a SkyWest regional jet, which nearly collided with a smaller aircraft that had failed to vacate a runway on which the SkyWest flight was landing. No one was injured.

SkyWest Airlines Flight SKW69R, a Canadair CRJ-200 aircraft, was arriving on a scheduled flight from Salt Lake City when the incident occurred. According to information provided by the NTSB, at approximately 21:07 local time a Piper PA-46 landed at Fresno on runway 29R. Before the aircraft had exited the runway, the tower controller cleared the SkyWest CRJ to land on the same runway. The SkyWest crew saw the Piper and veered to the right side of the runway, missing the other aircraft by an estimated 15 feet, wingtip to wingtip.

The NTSB notes that the incident occurred at night with 10 miles visibility.

NTSB investigating two runway incursions at Teterboro Airport

The U.S. National Transportation Safety Board (NTSB) has launched an investigation into two recent runway incursion incidents at New Jersey's Teterboro Airport (TEB). The first of the two incidents occurred on June 25, 2008, when a JetRide Learjet 45 flew over two airport workers at a height of 150 ft. and landed on a closed runway. The second incident occurred on July 9, 2008, when a Cessna 172 taxied across the hold line for a runway on which a Falcon 200 had just been cleared for take-off. No one was injured in either incident.

Here are details of the Learjet incident, from the NTSB Preliminary Incident Report (re-paragraphed for easier reading):

On June 25, 2008, at 5:34 am eastern daylight time, a runway incursion occurred at Teterboro Airport (TEB), Teterboro, New Jersey involving Windrider (WDR) flight 988, a Learjet 45, occurred during the midnight shift when there was one controller scheduled to be in the tower.

The Federal Aviation Administration reported that runway 1/19 had been closed by Airport Operations and confirmed by the controller. The controller placed two runway incursion devices (RID) at the local control position but did not inform approach control of the closure.

A lighted X had been placed on the runway at the departure end of runway 19.

The approach controller called the tower controller 27 minutes later to request a visual approach to runway 19 for WDR988. The tower controller approved the request. On the initial transmission, the tower controller cleared WDR988 to land on runway 19.

The airplane flew over two employees who were working north of the displaced threshold of runway 19, between taxiways L/A and B and landed on the runway. The displaced threshold is 770 feet from the approach end of runway 19. Closest estimated proximity was 150 feet vertical.

The controller was working the local control position for 7 hours and 21 minutes when the incident occurred. At the time of the incident it was daylight, the wind was calm, sky clear, with 10 statute miles visibility.

The initial review of data indicated that the controller sounded engaged and alert in his communications with aircraft and vehicles operating on the airfield. The controller was scheduled to work the midnight shifts each night from June 23 through June 26. The week before this event, the controller worked evening shifts (3:00 pm to 11:00 pm). The controller's statement reads in its entirety, "While performing required non-control duties WDR 988 landed on runway 19".

The automatic terminal information service (ATIS) information H did not mention the closed runway. [NTSB ID: OPS08IA009]

Here is what the NTSB had to say in a news release about the Cessna/Falcon incident:

On July 9, 2008, at 10:10 a.m. (EDT), a Cessna 172 (N316AS) and, a Dassault Falcon 200 (N277QS) were also involved in a runway incursion at Teterboro Airport.

The Cessna landed on runway 19 and requested a back taxi to the approach end of runway 19 for departure. The ground controller instructed the pilot to taxi to runway 19 via taxiway L and to hold short of runway 19. However, the pilot was not instructed to hold short of runway 24, which intersected runway 19.

The airplane had crossed the hold line for runway 24 but not over the runway edge when the tower controller cleared the Falcon for takeoff on runway 24. The tower cancelled the Falcon's clearance once it was determined that the Cessna was across the runway hold line. The FAA reported the two airplanes were 1,200 feet apart.

The incident occurred during the day shift with a front line manager and two air traffic control specialists on position.

Here are the NTSB Preliminary Incident reports about the second incident: NTSB ID: OPS08IA010A; NTSB ID: OPS08IA010B

NTSB Air Traffic Control Investigator Daniel Bartlett has been designated Investigator-in-charge for both incidents.

ALPA launches runway safety campaign

Just in case you haven't yet seen it (or haven't even heard about it) I'd like to encourage all readers of Professional Pilot News to go and take a look at Hold Short for Runway Safety, a new website run by the Air Line Pilots Association (ALPA). ALPA recently launched a campaign intended "to raise the awareness of the measures that can prevent runway hazards." The organization has launched this interesting website in support of their campaign.

The Hold Short for Runway Safety focuses on safety during ground operations. The stated goal is to prevent runway incursions, excursions, and confusion. It offers commonsense guidance for operating in the period "between getting in the cockpit and hitting Vr."

In addition to excellent background information about runway safety, runway incursions and pilot deviations, the interactive website features several runway incursion re-enactment videos, and a quiz about situational awareness through airfield signs and air traffic control instructions.

You can take an Online Runway Safety Education Program via the website and print out your certificate after completion. ALPA says, "If you are involved in a runway incursion event, this satisfies the FAA 'seminar' requirement for participation in the Runway Incursion Information Evaluation Program (RIIEP)."

Click on over to ALPA's Hold Short for Runway Safety website and get busy!

Video: Animations of runway incursion at PVD, with ATC audio

A reader sent me a link to an animation of a runway incursion that had been posted to YouTube. When I went to YouTube to view the video, I also saw a listing for another animation of the same event. Both animations include audio of communications between ATC and the aircraft that were on the ground, but neither indicated when this incident took place.

A little homework on my part revealed that the animations were of a runway incursion that took place in 1999 at T.F. Green Airport (PVD), Providence, Rhode Island. Here is a brief overview of that runway incursion from the NTSB website, followed by the two YouTube videos.

From the NTSB Board Meeting of June 13, 2000:

On December 6, 1999, at about 8:35 p.m., United Airlines flight 1448, a Boeing 757, was involved in a runway incursion on runway 5 Right at Theodore Francis Green State Airport, near Providence, Rhode Island. At the time of the incident, it was dark and the reported visibility was one-quarter mile.

After United 1448 landed on runway 5 Right, the tower controller instructed the flight crew to proceed to the terminal using taxiways November and Tango, and report crossing runway 16.

During their taxi in the fog, the flight crew became disoriented and turned onto taxiway Bravo by mistake. They then provided incorrect position reports to the tower controller. The airplane ended up at the intersection of Runway 16 and Runway 23 left. Note that Runways 23 Left and 5 Right are opposite ends of the same runway.

Shortly afterward, a Federal Express aircraft taking off from runway 5 Right passed very close to United 1448. The subsequent conversation between the tower controller and United 1448 shows continued uncertainty about the aircraft's position. For example, there will be several references to Runway 23 right while the airplane is actually on 23 left.

Here's the link to the 'official' NTSB animation of this PVD runway incursion of December 6, 1999. (You will need to use a player on your computer to view it.)

Keeping in mind that the two videos below are 'unofficial' simulations of the event, they are still worth watching.



Thanks to YouTube user B737ngdriver for the above video. The video was posted to YouTube in May of this year. If it does not display or play properly above, click here to view it on YouTube.

The next video is a bit longer, and although the depiction of the aircraft types and livery are inaccurate, it illustrates the event from a different (simulated) vantage point than the video above.



Thanks to YouTube user magnetoz, who posted the video in July of this year. If it does not display or play properly above, click here to view the runway incursion video on YouTube.

And a tip of the hat to the reader who sent me the link to the first video by email.

Full deployment of systems such as Airport Surface Detection Equipment-X (ASDE-X) and Automatic Dependent Surveillance Broadcast System (ADS-B) can not come soon enough!

FAA changes its official definition for 'runway incursions'

Today the Federal Aviation Administration (FAA) announced a change to its definition for what constitutes a runway incursion. Effective immediately, the FAA will use the same definition for runway incursions as the International Civil Aviation Organization (ICAO), as set forth in a new Fact Sheet:

The biggest difference between the two definitions is that ICAO defines a runway incursion as any unauthorized intrusion onto a runway, regardless of whether or not an aircraft presents a potential conflict. For the FAA, an incident without an aircraft in potential conflict — such as an unauthorized aircraft crossing an empty runway — was defined as a “surface incident” and not a runway incursion.

The new definition means that some incidents formerly classified as surface incidents will now be classified as C or D category runway incursions, which are low-risk incidents with ample time and/or distance to avoid a collision.

The FAA has always tracked surface incidents, in addition to runway incursions. The new definition simply means that certain less severe incidents will be classified differently. All incidents tracked in the past will continue to be tracked.

The classification of the most serious kinds of runway incursions, Categories A and B, remains unchanged. The total number of Category A and B incursions has fallen from 53 in fiscal year 2001 to 31 in FY 2006. A and B incursions are on track for another drop in FY 2007, with 24 recorded through Sept. 9.

The FAA made this change so that the same definition for runway incursions will apply worldwide. The hope is that the use of a single definition will help in the search to determine common factors that contribute to these incidents.

NTSB report on the latest LAX runway incursion

You may have seen some news reports about the most recent runway incursion at LAX. The incident happened on August, 16, 2007, and involved aircraft operated by WestJet and Northwest Airlines. No one was injured, but it certainly was a close call. After a preliminary investigation, the National Transportation Safety Board (NTSB) estimates that the two aircraft may have missed each other by less than 40 feet.

Here is a description of what happened, drawn from the NTSB's preliminary incident report:

On August 16, 2007, at approximately 12:57 Pacific daylight time, a runway incursion occurred involving West Jet (WJA) 900, B737 and Northwest Airlines (NWA) flight 180, an A320, at Los Angeles International Airport, Los Angeles, California.

WJA900 landed on runway 24R and exited at taxiway Y then changed to ground control frequency without authorization while the airplane was holding between the parallel runways.

The tower controller cleared NWA180 for takeoff from runway 24L. Meanwhile, the pilot of WJA900 contracted ground control and said, "Ground, WJA900 with you on reverse [taxiway] yankee for gate 35." The ground controller assumed that the tower controller had instructed the flight to cross runway 24L and responded, "WJA900, Los Angeles tower, taxi [via taxiway] echo to the gate."

Ten seconds later, the pilot of WJA900 confirmed that the flight was cleared to cross runway 24L. The ground controller asked who called and the pilot again asked whether or not they were cleared to cross the runway. The ground controller then realized that WJA900 had not been instructed to cross runway 24L and told WJA900 to stop.

According to the FAA and WJA, the airplane crossed the hold short line but did not enter the runway.

According to the FAA, the two aircraft missed colliding by 37 feet (wingtip of A320 to the nose of the B737) as NWA180 departed runway 24L. [NTSB Report No. OPS07IA009A]

The NTSB notes that the Airport Movement Area Safety System (AMASS) at LAX was operational at the time of the incident, but it is unknown whether or not it activated.

WestJet and Northwest jets have close call at LAX

It's been all over the news today: Another close call on the ground at Los Angeles International Airport (LAX) yesterday afternoon, ironically on the same day that the FAA announced new plans to improve runway safety! Fortunately a collision was avoided and no one was reported to have been injured in the incident.

According to news reports, a WestJet Boeing 737 aircraft arriving from Calgary nearly collided with a Northwest Airbus A320 that was taking off. Apparently the WestJet aircraft had landed and was taxiing. It nearly crossed an active runway into the path of the departing Northwest plane, but managed to stop just in time. Media reports say that the two aircraft came to within 50 feet of colliding.

An article on SFGate.com about the incident at LAX quoted FAA spokesman Ian Gregor who said that the incident "appeared to have begun when the arriving pilot prematurely switched radio frequencies from air traffic control to ground traffic control before receiving final instructions from the air traffic controller on whether to cross the runway."

Gregor said the tower air traffic controllers who handle landings also tell pilots whether they are then cleared to cross runways, and ground controllers direct planes afterward.

But the arriving pilot switched radio frequencies from air traffic control to ground traffic control before receiving final instructions, Gregor said.

The pilot then made a statement to the ground controller about using a taxi route to a gate, and the ground controller assumed the plane had already crossed the inner runway, Gregor said.

The Westjet pilot then apparently saw the Northwest jet on its takeoff roll and asked if clearance had been given, and the ground controller ordered the Westjet plane to stop, Gregor said.

At that point an automated collision avoidance alarm sounded in the tower, he said.

This incident was the seventh runway incursion at LAX this fiscal year.

FAA plans for runway safety improvements

The U.S. Federal Aviation Administration (FAA) is very concerned with the recent spate of close calls at U.S. airports, and rightly so. In an effort to address these serious aviation safety risks, a meeting was convened yesterday among more than 40 aviation leaders from airlines, airports, air traffic control and pilot unions, aerospace manufacturers, and the FAA to discuss ways to enhance safety during ground operation of aircraft, and in particular, to reduce the risk of runway incursions and wrong runway departures.

FAA Administrator Marion Blakey asked the meeting participants to consider solutions in four areas:

• cockpit procedures
• airport signage and markings
• air traffic procedures
• technology

A Fact Sheet about the meeting, issued today by the FAA, lists a five-point short-term plan arrived at by the meeting participants:

1. Within 60 days, teams of FAA, airport operators, and airlines will begin safety reviews at the airports where wrong runway departures and runway incursions are the greatest concern. The FAA is compiling the list of 20 to 30 airports based on a variety of safety risk factors, including the record of past incursions.
2. Within 60 days, disseminate information and training across the entire aviation industry.
3. Within 60 days, accelerate the deployment of improved airport signage and markings at the top 75 airports, well ahead of the June 2008 mandated deadline.
4. Within 60 days, review cockpit procedures and air traffic control (ATC) clearance procedures. This may include changing cockpit procedures to minimize pilot activities and distractions while an aircraft is moving on the ground and to make ATC instructions more precise.
5. Implement a voluntary self-reporting system for all air traffic organization safety personnel, such as air traffic controllers and technicians.

The Fact Sheet also says that "Mid- and long-term goal areas are being pursued to address maximizing situational awareness, minimizing pilot distractions, and eliminating runway incursions using procedures and technology."

Safety during ground operations has been compromised all too frequently in recent months, not just in the United States, but at airports around the world. Here is a sampling of runway accidents and safety incidents that I have written about in this blog, just since the beginning of 2007:

• February - Close calls at Denver International Airport
• March - Atlanta runway incursion causes aborted takeoff
• April - El Al accident on Paris airport taxiway
• June - SpiceJet B737 lands on wrong runway at Delhi
• July - NTSB classifies FLL runway incursion as 'pilot deviation'
• July - NTSB: Crew to blame for Comair Flight 5191 accident

That list represents some of the more well-publicized incidents. Unfortunately there have been many, many more.

NTSB classifies FLL runway incursion as 'pilot deviation'

Yesterday I posted a brief item here about a runway incursion incident at Fort Lauderdale-Hollywood International Airport (FLL) earlier this week. This morning the National Transportation Safety Board (NTSB) issued a preliminary synopsis of the incident. I must say, it's a chilling report:

On July 11, 2007, at 1437 Eastern daylight time a runway incursion occurred at the Fort Lauderdale-Hollywood Airport, (FLL), Fort Lauderdale, Florida between United (UAL) flight 1544, an A-320 and Delta Airlines (DAL) flight 1489, a Boeing 757. The incident occurred in day visual flight rules conditions, visibility 10 miles, scattered clouds at 4,800 feet.

The FLL ground controller (GC) instructed UAL1544 to taxi to runway 9L via taxiways T7, D, and B. As the flight was taxiing on taxiway D near runway 9L, the tower local controller (LC) noticed the airplane was going too fast to hold short of the runway. LC told the GC to tell UAL to stop. The GC said "UAL 1544 stop, stop, stop". The crew stopped on runway 9L, 30 feet from the centerline.

DAL1489 was inbound for landing on runway 9L when LC determined that UAL1544 was not going to hold short of the runway. LC instructed DAL1489 to go around. When the crew received the instruction, the main landing gear was on the ground. According to the crew statement, they noted the urgency in the controller's voice so they knew they had to get the aircraft airborne. FAA reported DAL1489 flew over UAL1544 by less than 100 feet.

According to the FAA, the UAL crew stated they missed the turn onto taxiway B. [NTSB ID: OPS07IA006A]

A press release I received by email from the NTSB also states:

Fort Lauderdale International Airport is not equipped with either a ground safety system such as an Airport Movement Area Safety System or Airport Surveillance
Detection Equipment.

The United crew stated that they missed the turn onto taxiway B. The FAA has classified this incident as a pilot deviation.

FLL runway incursion on July 11, 2007

An article in the Miami Herald  reports that two aircraft came within 100 feet of colliding at Fort Lauderdale-Hollywood International Airport (FLL) yesterday.

According to the article, Delta Flight 1489, inbound from ATL, was on approach to FLL when a plane operated by United Airlines "missed its turn onto a taxiway and entered the runway where the other was about to land." The Delta flight executed a go-around. United Flight 1544 subsequently departed for Washington-Dulles without further incident.

The Miami Herald article notes:

The Fort Lauderdale-Hollywood airport had three runway incursions during the 12 months that ended May 31, according to FAA records. Two were blamed on pilot error and the third was ruled an air traffic control error. Nationwide, the FAA reported 330 runway incursions in fiscal year 2006.

The FAA is investigating the incident.

UPDATE: Here is the link to the NTSB factual report on this incident: The NTSB has classified this incident as a 'pilot deviation.

Atlanta runway incursion causes aborted takeoff

A Delta Air Lines Boeing 767 that had just begun its takeoff roll had to abort after a controller mistakenly cleared two other aircraft to taxi across the runway into the path of the departing aircraft. The Delta flight aborted the takeoff, turned onto a taxiway and rejoined the line-up for its departure to Los Angeles.

The incident happened at Atlanta's Hartsfield-Jackson International Airport. This was the second aborted takeoff due to controller error at that airport in three months.

Here is an account of what happened, as reported by the Atlanta Journal-Constitution:

The controller cleared Delta 509 at about 12:10 p.m. to take off on Runway 26 Left, which is about 10,000 feet long. Fourteen seconds later, the same controller cleared a Midwest Airlines Boeing 717 and an ASA CRJ to taxi across the runway downfield.

The Midwest jet had moved onto the runway and the ASA plane had crossed the "hold short" line that separates the taxiway from the runway when alarms in the control tower alerted air traffic controllers of the danger. The controller cancelled Delta Flight 509's takeoff while the plane was traveling about 40 miles an hour, then slowed and turned off the runway. It got back in line for takeoff and left uneventfully a few minutes later.

The Delta and Midwest planes were about 3,500 feet apart at their nearest point.

Gary Brittain, a veteran controller at Hartsfield-Jackson, said mistakes are being made at the Atlanta tower because controllers are being short-staffed and overworked.

"This is the kind of thing that happens when you've got controllers working six-day weeks, week after week," he said. "They're beginning to crack a little."

The controller who reportedly caused the incident was decertified, subject to retraining.

[Photo Source]