email correspondence 5/31

0183-EX-PL-2016 Text Documents

Caterpillar, Inc.

2016-05-31ELS_177444

Anthony Serafini From: Richard D. Rubino <rdr@bloostonlaw.com> Sent: Tuesday, May 31, 2016 2:21 PM To: Nnake Nweke Cc: Anthony Serafini Subject: Caterpillar - File No. 0183-EX-PL-2016 Importance: High Mr. Nweke – To follow up on my voice mail to Mr. Serafini, on May 18, 2016, the above‐referenced application was dismissed for failure to respond to an April 1, 2016 e‐mail request for information from Mr. Serafini. Mr. Gunkel has indicated to me that he did not receive Mr. Serafini’s April 1, 2016 email even though it appears to have been properly addressed. Based upon the non‐receipt of this e‐mail, it is respectfully requested that the application be returned to a pending status and that Caterpillar be provided information for obtaining the appropriate prior coordination from AFTRCC. Additionally, it would be beneficial if you could advise which frequencies in the above‐referenced Caterpillar application are the subject of the NTIA request for frequency coordination through AFTRCC. Thank you for your assistance, Richard Rubino Richard D. Rubino Blooston, Mordkofsky, Dickens, Duffy & Prendergast, LLP 2120 L Street, NW Suite 300 Washington, DC 20037 Tel. (202) 828-5519 Fax. (202) 828-5568 This message and any attached documents contain information which may be confidential, subject to privilege or exempt from disclosure under applicable law. These materials are intended only for the use of the intended recipient. If you are not the intended recipient of this transmission, you are hereby notified that any distribution, disclosure, printing, copying, storage, modification or the taking of any action in reliance upon this transmission is strictly prohibited. Delivery of this message to any person other than the intended recipient shall not compromise or waive such confidentiality, privilege or exemption from disclosure as to this communication. If you have received this communication in error, please immediately notify the sender and delete the message from your system. 1


Document Created: 2016-05-31 14:34:20
Document Modified: 2016-05-31 14:34:20
© 2026 FCC.report
This site is not affiliated with or endorsed by the FCC