Apollo Settles Alleged Sanctions Violations: Aircraft Lessors Pay Attention

The Office of Foreign Assets Control (OFAC) of the U.S. Department of the Treasury has broad delegated authority to administer and enforce the sanctions laws and related sanctions programs of the United States. As a key component of its enforcement authority, OFAC may investigate “apparent violations” of sanctions laws and assess civil monetary penalties against violators pursuant to five statutes, including the Trading with the Enemy Act and the International Emergency Economic Powers Act.1

An “apparent violation” involves “conduct that constitutes an actual or possible violation of U.S. economic sanctions laws.”2 An OFAC investigation of an “apparent violation” may lead to one or more administrative actions, including a “no action” determination, a request for additional information, the issuance of a cautionary letter or finding of violation, the imposition of a civil monetary penalty and, in extreme cases, a criminal referral.3 Investigations of apparent violations by OFAC often lead to negotiated settlements where a final determination is not made as to whether a sanctions violation has actually occurred.4

Upon the conclusion of a proceeding that “results in the imposition of a civil penalty or an informal settlement” against or with an entity (as opposed to an individual), OFAC is required to make certain basic information available to the public.5 In addition, OFAC may release on a “case-by-case” basis “additional information” concerning the penalty proceeding,6 and it often does. Such additional information will sometimes include informal compliance guidance, cautionary reminders and best practices recommendations. Such information is routinely consumed by corporate compliance officers seeking fresh insight on ever-evolving compliance and enforcement trends, particularly in the context of proceedings relating to industries with which they are involved.

On November 7, 2019, OFAC released enforcement information that has caught the attention of the aircraft leasing community, particularly U.S. aircraft lessors and their owned or controlled Irish lessor subsidiaries.7 The matter involved a settlement by Apollo Aviation Group, LLC8 of its potential civil liability for apparent violations of OFAC’s Sudanese Sanctions Regulations (SSR) that existed in 2014–5.9 Although the amount of the settlement was relatively modest, the enforcement activity by OFAC in the proceeding has attracted scrutiny by aircraft lessors because, for the first time in recent memory, a U.S. aircraft lessor has paid a civil penalty to OFAC for alleged sanctions violations.

At the time of the apparent violations, Apollo was a U.S. aircraft lessor which became involved in two engine leasing transactions that came back to haunt it.

In the first transaction, Apollo leased two jet engines to a UAE lessee which subleased them to a Ukrainian airline with which it was apparently affiliated. The sublessee, in turn, installed both engines on an aircraft that it “wet leased”10 to Sudan Airways, which was on OFAC’s List of Specially Designated Nationals and Blocked Persons within the meaning of the “Government of Sudan.” Sudan Airways used the engines on flights to and from Sudan for approximately four months before they were returned to Apollo when the lease ended. Meanwhile, in a separate transaction, Apollo leased a third jet engine to the same UAE lessee, which subleased the engine to the same Ukrainian airline, which installed the engine on an aircraft that it also wet leased to Sudan Airways. Sudan Airways used the third engine on flights to and from Sudan until such time as Apollo discovered how it was being used and demanded that the engine be removed from the aircraft.

Both leases between Apollo and its UAE lessee contained restrictive covenants “prohibiting the lessee from maintaining, operating, flying, or transferring the engines to any countries subject to United States or United Nations sanctions.”11 Thus, by allowing the engines to be installed by its sublessee on aircraft that were eventually wetleased to Sudan Airways, and flown to and from Sudan during the country’s embargo, the lessee presumably breached the operating restrictions and covenants imposed by Apollo in the leases. Moreover, once Apollo learned that the first two engines had been used, and the third engine was being used, for the benefit of Sudan Airways, it demanded that the third engine be removed from the aircraft that the sub-lessee had wet-leased to Sudan Airways, and this was done.12

One might reasonably conclude from these facts that Apollo acted like a good corporate citizen. So what did Apollo do wrong from a sanctions compliance standpoint?

OFAC stated that Apollo may have violated section 538.201 of the SSR, which at the time “prohibited U.S. persons from dealing in any property or interests in property of the Government of Sudan,”13 as well as section 538.205 of the SSR, which at the time “prohibited the exportation or re-exportation, directly or indirectly, of goods, technology or services, from the United States or by U.S. persons to Sudan.”14

What are the takeaways and possible lessons to be drawn by aircraft lessors from this settlement based upon these alleged violations and the facts upon which they were based?

First, according to OFAC, Apollo did not “ensure” that the engines “were utilized in a manner that complied with OFAC’s regulations,” notwithstanding lease language that effectively required its lessee to comply.15 OFAC is clearly suggesting here that aircraft lessors have a duty to require sanctions compliance by their lessees. And, in view of the fact that many sanctions programs are enforced on a strict liability basis, OFAC’s comment that Apollo failed to “ensure” compliance by its lessee and sublessees makes sense. Apollo was not in a position to avoid civil liability by hiding behind the well-drafted language of its two leases. If a sanctions violation occurred for which Apollo was strictly liable, the mere fact that its lessee’s breach of the lease was the proximate cause of the violation would not provide a safe harbor.

As an example of Apollo’s alleged failure to “ensure” legal compliance, OFAC observed that Apollo did not obtain “U.S. law export compliance certificates from lessees and sublessees,”16 a comment which is somewhat puzzling. To our knowledge, there is nothing in the law requiring a lessor to obtain export compliance certificates, at least not in circumstances where an export or re-export license is not otherwise required in connection with the underlying lease transaction. Moreover, as a practical matter, it would be difficult, at best, for an aircraft lessor to force the direct delivery of certificates from a sublessee or sub-sub-lessee with whom it lacks privity of contract. In view of the foregoing, one assumes that OFAC was looking for Apollo to install procedures by which its lessee would self-report on a regular basis its own compliance (and compliance by downstream sublessees) with applicable export control laws and the relevant sanctions restrictions contained in the lease.

Second, OFAC found that Apollo “did not periodically monitor or otherwise verify its lessee’s and sublessee’s adherence to the lease provisions requiring compliance with U.S. sanctions laws during the life of the lease.”17 In this regard, OFAC observed that Apollo never learned how and where its engines were being used until after the first two engines were returned following lease expiration and a post-lease review of engine records, including “specific information regarding their use and destinations,” actually conducted.

In view of the foregoing, OFAC stressed the importance of “companies operating in high-risk industries to implement effective, thorough and on-going, risk-based compliance measures, especially when engaging in transactions concerning the aviation industry.”18 OFAC also reminded aircraft and engine lessors of its July 23, 2019, advisory warning of deceptive practices “employed by Iran with respect to aviation matters.”19 While the advisory focused on Iran, OFAC noted that “participants in the civil aviation industry should be aware that other jurisdictions subject to OFAC sanctions may engage in similar deception practices.”20 Thus, according to OFAC, companies operating internationally should implement Know Your Customer screening procedures and “compliance measures that extend beyond the point-of-sale and function throughout the entire business of lease period.21

As a matter of best practices, aircraft lessors should implement risk-based sanctions compliance measures throughout the entirety of a lease period, and most do. Continuous KYC screening by lessors of their lessees and sublessees is a common compliance practice. Periodic reporting by lessees as to the use and destination of leased aircraft and engines appears to be a practice encouraged by OFAC.22 Lessors can also make it a regular internal practice to spot check the movement of their leased aircraft through such web-based platforms as Flight Tracker and Flight Aware. If implemented by lessors, such practices may enable early detection of nascent sanctions risks and violations by their lessees and sublessees.

Finally, OFAC reminded lessors that they “can mitigate sanctions risk by conducting risk assessments and exercising caution when doing business with entities that are affiliated with, or known to transact business with, OFAC-sanctioned persons or jurisdictions, or that otherwise pose high risks due to their joint ventures, affiliates, subsidiaries, customers, suppliers, geographic location, or the products and services they offer.” Such risk assessment is an integral part of the risk-based sanctions compliance program routinely encouraged by OFAC, as outlined in its Framework for OFAC Compliance Commitments on May 2, 2019.23 For aircraft and engine lessors, conducting pre-lease due diligence on the ownership and control of prospective lessees and sublessees, as well as the business they conduct, the markets they serve, the equipment they use and the aviation partners with whom they engage, are key to identifying and understanding the sanctions risks that a prospective business opportunity presents.


See U.S. Department of the Treasury, Office of Foreign Assets Control, Inflation Adjustment of Civil Monetary Penalties, Final Rule, 84 Fed. Reg. 27714, 27715 (June 14, 2019).

2 31 C.F.R. Part 501, Appendix A, Section I.A.

3 31 C.F.R. Part 501, Appendix A, Section II.

4 31 C.F.R. Part 501, Appendix A, Section V.C.

5 31 C.F.R. §501.805(d)(1). Such information includes “(A) [t]he name and address of the entity involved, (B) [t]he sanctions program involved, (C) A brief description of the violation or alleged violation, (D) [a] clear indication whether the proceeding resulted in an informal settlement or in the imposition of a penalty, (E) [a]n indication whether the entity voluntarily disclosed the violation or alleged violation to OFAC, and (F) [t]he amount of the penalty imposed or the amount of the agreed settlement.” Id. OFAC communicates all such information through its website. 31 C.F.R. § 501.805(d)(2).

6 31 C.F.R. § 501.805(d)(4).

See OFAC Resource Center, Settlement Agreement between the U.S. Department of the Treasury’s Office of Foreign Assets Control and Apollo Aviation Group, LLC (Nov. 7, 2019) (https://www.treasury.gov/resource-center/sanctions/OFAC-Enforcement/Page…) (the Settlement Announcement).

8 In December 2018, Apollo was acquired by The Carlyle Group and currently operates as Carlyle Aviation Partners Ltd. According to the Settlement Announcement, neither The Carlyle Group nor its affiliated funds were involved in the apparent violations at issue. See id. at 1 n.1.

See 31 C.F.R. Part 538, Sudanese Sanctions Regulations (7-1-15 Edition). Note that most sanctions with respect to Sudan were effectively revoked by general license as of October 2, 2017, thereby authorizing transactions previously prohibited by the SSR during the time period of the apparent violations by Apollo. However, as is true when most sanctions programs are lifted, the general license issued in the SSR program did not “affect past, present of future OFAC enforcements or actions related to any apparent violations of the SSR relating to activities that occurred prior to the date of the general license.” Settlement Announcement at 1 n.2. See also OFAC FAQ 532 (https://www.treasury.gov/resource-center/faqs/Sanctions/Pages/faq_other.aspx#sudan_whole). 

10 A “wet lease” is “an aviation leasing arrangement whereby the lessor operates the aircraft on behalf of the lessee, with the lessor typically providing the crew, maintenance and insurance, as well as the aircraft itself.” See Settlement Announcement at 1 n.3.

11 Id. at 1.

12 Unfortunately, Apollo did not learn that the first two engines were used in violation of lease restrictions until they were returned following lease expiration and it conducted a post-lease review of the relevant engine records. 

13 The alleged application of section 538.201 to Apollo in the circumstances confirms the broad interpretive meaning that OFAC often ascribes to terms such as “interest,” “property,” “property interest” and “dealings,” which appear in many sanctions programs.

14 The alleged application of section 538.205 to Apollo in the circumstances suggests that a U.S. lessor of aircraft and jet engines may be tagged with the “re-export” of such goods and related services from one foreign country to another, notwithstanding the existence of a contractual daisy-chain of lessees, sub-lessees, and/or wetlessees that actually direct and control such flight decisions. In the context of U.S. export control laws, the Export Administration Regulations (EAR) define the term “re-export” to include the “actual shipment or transmission of an item subject to the EAR from one foreign country to another foreign country, including the sending or taking of an item to or from such countries in any manner.” 15 C.F.R. § 734.14(a)(1). Thus, for export control purposes, the flight of an aircraft subject to the EAR from one foreign county to another foreign country constitutes a “re-export” of the aircraft to that country. 

15 Settlement Announcement at 1.

16 Id.

17 Id., at 1–2.

18 Id. at 3. (emphasis added).

19 IdSee OFAC, Iran-Related Civil Aviation Industry Advisory (July 23, 2019) (https://www.treasury.gov/resource-center/sanctions/OFAC-Enforcement/Pages/20190723.aspx)

20 Id.

21 Id. (emphasis added).

22 In Apollo, OFAC reacted favorably to certain steps alleged to have been taken by Apollo to minimize the risk of the recurrence of similar conduct, including the implementation of procedures by which Apollo began “obtaining U.S. law export compliance certificates from lessees and sublessees.” Id.

23 See https://www.treasury.gov/resource-center/sanctions/Documents/framework_ofac_cc.pdf.


© 2019 Vedder Price

More sanctions actions on the National Law Review Antitrust & Trade Regulation law page.

Raise Your Hand If You’re Confused about I-9 Reverifications for Employees with TPS

Temporary Protected Status (TPS) is a humanitarian benefit available to foreign nationals who are unable to return to their home countries because of certain temporary conditions including ongoing armed conflict such as civil war, an environmental disaster like an earthquake, hurricane, epidemic, or other extraordinary conditions. During TPS designation, qualifying foreign nationals are not removable from the US and can obtain work authorization and travel permission.

The Department of Homeland Security (DHS) has recently terminated TPS for nationals of El Salvador, Haiti, Nicaragua, and Sudan but has granted a period of orderly departure to allow time for this population to wind up their affairs in the US. This has left employers in a quandary about which TPS holders remain able to work and how to comply with Form I-9 Employment Eligibility Verifications.

To help ease the confusion, the chart below illustrates TPS-designated countries, the dates by which beneficiaries were required to re-register and, for those who do re-register, how long their current Employment Authorization Cards (EAD) are automatically extended pending decisions of EAD renewal applications. The TPS termination dates for El Salvador, Haiti, Nicaragua, and Sudan are also included.

Country

Re-Registration Period Ends

EAD Auto-Extended Until

TPS End Date

El Salvador

03/19/2018

09/05/2018

09/09/2019

Haiti

03/19/2018

07/21/2018

07/22/2019

Honduras

02/13/2018

07/04/2018

Nepal

12/27/2016

06/24/2017

Nicaragua

02/13/2018

07/04/2018

01/05/2019

Somalia

03/20/2017

South Sudan

11/20/2017

05/01/2018

Sudan

12/11/2017

05/01/2018

11/12/2018

Syria

09/30/2016

03/31/2017

Yemen

03/06/2017

09/03/2017

As reflected in the chart above, sometimes DHS issues a blanket automatic extension of the expiring EADs for TPS beneficiaries of a specific country in order to allow time for EADs with new validity dates to be issued. The automatic extension periods are available to those TPS beneficiaries who timely re-register and apply to renew their EADs.

Although an employer cannot specify which documents an employee can present in connection with the I-9 Employment Eligibility Verification process, TPS beneficiaries with automatic EAD extensions may present an expired EAD bearing the C19 eligibility code along with a Form I-797C Notice of Action indicating the eligibility category code A12 or C19. The codes need not be the same.

The M-274 Handbook for Employers is an excellent resource in determining how to complete the Form I-9 for those employees with automatic EAD extensions. It specifies that:

“For a current employee, update Section 2 of Form I-9 with the new expiration date as follows:

  • Draw a line through the old expiration date and write the new expiration date in the margin of Section 2;

  • Write EAD EXT in Section 2;

  • Initial and date the correction.”

For TPS beneficiaries, the new expiration date should correspond with the respective date as noted in the chart above. An employee whose employment authorization is automatically extended along with his/her EAD may cross out the “employment authorized until” date in Section 1, write the new expiration date as reflected in the chart, initial and date the change.

A new employee may present the expired EAD and Form I-797C Notice of Action indicating USCIS’s receipt of the employee’s timely filed renewal application. When completing Section 1, the employee should enter the corresponding date from the chart in the “employment authorized until mm/dd/yyyy” field.

When completing Section 2, the employer should enter into the Expiration Date field the date the automatic extension period expires, not the expiration date on the face of the expired EAD. The employer should enter the receipt number from the I-797C Notice of Action as the document number on Form I-9. Note that reverification is required when the employee’s automatic extension ends.

While an employer is not required to be an expert in I-9 documents and review, having access to reliable resources comes in handy and will take you to the head of the class.

 

Copyright © 2018 Womble Bond Dickinson (US) LLP, All Rights Reserved.
This post was written by Jennifer Cory of Womble Bond Dickinson (US) LLP.

US State Department Clarifies Implementation of Travel Ban Exemptions

The diplomatic cable instructs consulates on how to interpret the US Supreme Court’s direction to enforce the restriction only against foreign nationals who lack a “bona fide relationship with a person or entity in the United States.”

This Immigration Alert serves as an addendum to our prior summary of the Supreme Court decision partially granting the government’s request to stay enforcement of two preliminary injunctions that temporarily halted enforcement of Executive Order (EO) No. 13780. As a result of this decision, foreign nationals from six countries (Libya, Somalia, Sudan, Syria, Iran, and Yemen) who cannot show bona fide ties to the United States may be denied visas or entry for 90 days starting Thursday, June 29 at 8:00 p.m. EDT.

The communication from the US Secretary of State’s office enumerates the following situations where the EO’s travel restrictions will not apply:

  • When the applicant has a close familial relationship in the United States, which is defined as a parent (including parent-in-law), spouse, fiancé, child, adult son or daughter, son-in-law, daughter-in-law, or sibling, whether whole or half. This includes step relationships, but does not include grandparents, grandchildren, aunts, uncles, nieces, nephews, cousins, brothers-in-law and sisters-in-law, or any other “extended” family members.

  • When the applicant has a formal, documented relationship with an entity formed in the ordinary course, rather than for the purpose of evading the EO. This includes established eligibility for a nonimmigrant visa in any classification other than a B, C-1, D, I, or K, as a bona fide relationship to a person or entity is inherent in the visa classification.

  • When there are eligible derivative family members of any exempt applicant.

  • When the applicant has established eligibility for an immigrant visa in the immediate relative, family-based, or employment-based classification (other than certain self-petitioning and special immigrant applicants).

  • When the applicant is traveling on an A-1, A-2, NATO-1 through NATO-6, C-2 for travel to the United Nations, C-3, G-1, G-2, G-3, or G-4 visa, or a diplomatic-type visa of any classification.

  • When the applicant has been granted asylum, is a refugee who has already been admitted to the United States (including derivative follow-to-join refugees and asylees), or is an individual who has been granted withholding of removal, advance parole, or protection under the Convention Against Torture.

Applicants admitted or paroled into the United States on or after the date of the Supreme Court decision are also exempted, as are those currently in the United States who can present a visa with a validity period that includes either January 27, 2017 (the day the EO was signed) or June 29, 2017. Any document other than a visa, such as an advance parole document, valid on or after June 29 will also exempt the holder.

As described in the prior alert, any lawful permanent resident or dual foreign national of one of the six named countries who can present a valid passport from a country not on the list is not impacted by the EO. The EO also permits consular officers to grant case-by-case waivers to otherwise affected applicants who can demonstrate that being denied entry during the 90-day period would cause undue hardship, that entry would not pose a threat to national security, and that their admission would be in the national interest.

This post was written by Eric S. Bord and Eleanor Pelta of  Morgan, Lewis & Bockius LLP.